Sam A. Horvath-Hunt
Sam A. Horvath-Hunt
A new issue has arisen with this as of #45. Where the following was (maybe?) working before, the type system is now unable to determine if `A` constitutes the value...
@ericblade Does #46 clear things up at all?
These could return `NonEmptyArray` as our sum types must always have at least one constructor. (Fun note: Apparently they needn't in Haskell, `data X` is a valid declaration.) `Member` (non-literal)...
You're right, if typechecking is limited to the editor then we'd be losing type safety versus compiling directly via intlc first and then running tsc. Might it be worth considering...
This is relevant to linting output as well as of #179. It's unclear how well this would scale. The object may be large and the message mayn't be at the...
If we do this we may want to consider giving our superset its own name.
Note that as the spec is currently written, if we support MF2 (#156), we'll once again be supporting a superset.
Copied from the linked issue: --- That's interesting. I suppose it'd be analagous to `other`. Where `other` widens e.g. `'a' | 'b'` to `string` (encoded conveniently via a union), `null`...
How could we prevent the following without introducing our own typechecking?: ``` {x} {x, nullable, null {} other {{x}}} ``` In the above design `x` is probably `string | null`...
@OliverJAsh I don't think we can leave this for userland. This'd be a type error on output: ``` {x, number} {x, nullable, null {} other {}} ``` Where `number |...