You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to do this by pressing Ctrl+Alt+M (make-case) with the cursor over ?argType (or having it fully selected)--but this seems to only work when this type signature is not followed by any code on the next line, i.e. when at least one full newline separates it from the definition. When the definition follows the type signature, as it usually does, the whole type signature with the newly-created case expression seems to be inserted into half of the definition.
I think I noticed this before in some regular (non-type-signature) case-expressions as well.
Screenshots for illustration:
Broken
Works when a newline separates the signature and the definition
I think this may also be related to the broken syntax-highlighting, also visible from the screenshots.
The text was updated successfully, but these errors were encountered:
Thanks for the bug report. I'll look into this. As a suggestion: it would be helpful to include code snippets (enclosed in triple backticks) instead of screenshots. That gives us some code to work with immediately.
Ch. 6 in Type-driven development has you case-split on a hole that is inside a type signature:
I tried to do this by pressing Ctrl+Alt+M (make-case) with the cursor over
?argType
(or having it fully selected)--but this seems to only work when this type signature is not followed by any code on the next line, i.e. when at least one full newline separates it from the definition. When the definition follows the type signature, as it usually does, the whole type signature with the newly-created case expression seems to be inserted into half of the definition.I think I noticed this before in some regular (non-type-signature) case-expressions as well.
Screenshots for illustration:
I think this may also be related to the broken syntax-highlighting, also visible from the screenshots.
The text was updated successfully, but these errors were encountered: