Adrian Kunz
Adrian Kunz
So, how do I actually register an alias now? `FMLControlledNamespacedRegistry.addAlias(String, String)` is package private, and `GameRegistry.addAlias(String, String, GameRegistry.Type)` is a no-op.
So we can conclude that the Alias System works **syntactically**, but not **semantically**. Here is a list of things that should be improved. 1. A substitution should not be forced...
This is a general problem with throw "expressions": ```swift let x = throw new RuntimeException print(throw new RuntimeException) ```
Hm, actually I already have a type like `never` (although it's called `none`). It is a subtype of every type and also the type that is inferred when using a...
Well the type system treats it differently because it is a bottom type. Also, it makes the difference between „function f():void returns nothing“ and „function g():none never returns at all“....
Yes, there is no unreachable code detection at all in the language. The compiler is not sophisticated enough for that and retrofitting it is a pain.
@phase what do you mean, specifically? A way to set an overload resolution priority for a method in case there are ambiguities?
I see where it can be useful: ``` swift // using the functions from the issue example var b = 1 < 2 // ambiguous, could be inferred as boolean...
The feature has just been implemented under [Issue #300 OverloadPriority Annotation](https://github.com/Dyvil/Dyvil/issues/300)
> Can you rebase this please to the latest `develop`? (Instead of rebasing it's easier to cherry-pick it probably.) Done!