Sam A. Horvath-Hunt
Sam A. Horvath-Hunt
I'd be inclined towards a newtype. It's too easy to mistakenly use or mix with your alias' underlying type, the same reason I've avoided branded types from io-ts. The trade-off,...
Thought about this a bit more. I'm thinking this isn't something that a downstream library can really do - it wouldn't even be compatible with fp-ts which uses `void`, which...
The TS plugin should have access to the `ScriptElementKind` enum. It's possible things can be improved for the plugin before this is implemented here.
This should also encompass supporting the following (not limited to "namespaces" per se): ```ts type A = B.C ``` ```hs type A = B.C D ```
^ Comes up with asterisk imports in docs-ts for example: ```ts export declare const readFile: (path: string, encoding: string) => TE.TaskEither ```
N.B. Nested namespaces are supported but seem to have a different generated structure in TS playground: ```ts export namespace A { export type X = number export namespace B {...
This might also be an effective, reliable way to test performance.
Workaround was needed for me as of last month, not checked without it since.
For what it's worth I'm seeing similar issues in Neovim where for example I can bind `Enter` but not `S-Enter`.
A little while ago I wrote a module in my xmonad "app" to dynamically fetch and parse the JSON-encoded pywal colors. A bonus with this approach is that they're refreshed...