Never in TypeScript is the equivalent of "bottom" where a value can never appear. The type holes in hazel are for incomplete types (during development) and work more like the any type in typescript where they are…
I don't think you do. The --in param on svg-term-cli worked for me locally.
I agree with regards to checked exceptions. Unfortunately Java doesn't support any form of polymorphism over thrown exceptions so it makes your code much harder to reuse. In languages that support polymorphic effects I…
I'm not sure I understand your point. Typed holes aren't trying to get rid of the concept of interfaces or well designed abstractions. Rather they aim to help deal with incomplete programs that are still under…
If you put the cursor on it you'll see an error message at the bottom. In this case the case expression is inexhaustive because it's only handling lists of size 0, 1, and 2.
I think the above commenter is more critiquing the notion of relying on intuition all together.
Most are, but I have definitely worked on projects that weren't
Possibly add a merge trees feature?
I'd rather find a better long term fit quicker than have a pleasant process when looking.
Never in TypeScript is the equivalent of "bottom" where a value can never appear. The type holes in hazel are for incomplete types (during development) and work more like the any type in typescript where they are…
I don't think you do. The --in param on svg-term-cli worked for me locally.
I agree with regards to checked exceptions. Unfortunately Java doesn't support any form of polymorphism over thrown exceptions so it makes your code much harder to reuse. In languages that support polymorphic effects I…
I'm not sure I understand your point. Typed holes aren't trying to get rid of the concept of interfaces or well designed abstractions. Rather they aim to help deal with incomplete programs that are still under…
If you put the cursor on it you'll see an error message at the bottom. In this case the case expression is inexhaustive because it's only handling lists of size 0, 1, and 2.
I think the above commenter is more critiquing the notion of relying on intuition all together.
Most are, but I have definitely worked on projects that weren't
Possibly add a merge trees feature?
I'd rather find a better long term fit quicker than have a pleasant process when looking.