Richard Gibson

Okay sure. I've created a PR https://github.com/Richiban/cChoco/pull/1 -- I'm not asking you to actually merge it in but just to demonstrate what I meant. Thanks

While I also think @dragomirtitian 's solution is a reasonable one, I'd like something more in keeping with Typescript's philosophy of not introducing any new syntax other than type annotations....

@dragomirtitian > Let's not consider :: as a new way to introduce a type annotation, but rather an empty rename. Works for me! 👍

I also support the concept of global usings in the project file. Although there'd be no way top opt out of these auto-usings per file, so it's possible there'd be...

I like the ability to declare `static interface`s from Option(2), but I'm not sure I would go with the limitation that static classes *can only* implement static interfaces. I can...

I don't like the idea of using parameter names as part of the matching algorithm, because IMO it gives parameter names an unwelcome, far-reaching significance. For example, if I have...

I thought I'd talk about a really cool use case for this: in Kotlin "contexts" can also be defined for operators. A domain I'm working in a lot right now...

One question that I think we need to ask (and I haven't seen anyone ask elsewhere) is whether the case classes can be used as types. Allow me to illustrate...

@mcintyre321 Your `OneOf` type can be described as equivalent to the `Either` type or `Choice` type such as that found in F#. However, the `Either` type is not an alternative...

@mcintyre321 I don't doubt it's usefulness (or the fact that it's better than `Either` at those situations). My point was that discriminated unions are a much more general tool that...