4 ms·
Well, this code in particular is presented as "hey there's no context." If I were to try to extract this, I would take each of those lets and make them an argum
by steveklabnik 9y ago
Well, this code in particular is presented as "hey there's no context." If I were to try to extract this, I would take each of those lets and make them an argument, then see what the compiler says for the return type, done.
- Lerc 9y agoHow do you find out what the compiler says for the return type? Is that covered in the book somewhere? I feel like this might help me quite a bit in my struggles.
- bbatha 9y agoI commonly let the compiler error out by specifying the wrong type or leaving off a type annotation. For instance, https://is.gd/8lLrY8 https://is.gd/8lLrY8
- steveklabnik 9y agoone way is to do return SOME_EXRPRESSION; and then look at the compiler error. Another way is let () = SOME_EXPRESSION; which works as long as SOME_EXPRESSION is not of type (), but if it compiles, well, you know the type :) Another way is to use some sort of IDE integration that gives you "show me the type on hover".
- pjmlp 9y agoThis is one example where having a REPL would help a lot. That is how I check such types outside IDEs in other ML derived languages.
- deleted 9y ago[deleted]
- roblabla 9y agoTBF, you can just do let _ : () = /* some expr whose type you don't know */ And compile it. It will quickly fail with a type error, giving you the full type of the expression.
- pjmlp 9y agoYeah, but it feels like a kluge, specially when used to F# on Visual Studio.