Aurea
Aurea
Prusti should also forbid using other spec-only constructs in regular code. For example, `old` or `time_credits` (#1275). A similar check is already implemented for user-defined `predicate!` functions, it needs to...
Looks like there is an `impl` type, which we don't fully support yet.
Yes, for now. I will probably put `ammer` and `ammer-core` on haxelib once #53 is completed.
I realise now that thx seems to be mostly a port of BigInteger.js also. Well I wasted my time :D https://github.com/Aurel300/hx-bigint
Why introduce a keyword for `downcast` instead of adding a `Std.downcast`? Is it to avoid spelling out the type in the case that the variable is already declared of type...
How do we express this in the AST? An extra (nullable) flag on [`haxe.macro.FunctionArg`](https://api.haxe.org/haxe/macro/FunctionArg.html) that can only be used on constructors?
Previous discussion here: https://github.com/HaxeFoundation/haxe/issues/6607 (@simn is it still used for completion somehow?)
But why call it `NoUse`? Why not `Unit` (since as far as I can tell this type is not *similar* to unit type, it *is* a unit type)? Why not...
@frabbit Top and bottom types are different concepts, unrelated to unit types. Top types correspond to Haxe's `Any` or `Dynamic`. Bottom types correspond to e.g. Rust's `!` type and indicate...
@frabbit I agree with you here: > but the proposal says `We want any type in function return type position to unify with NoUse hence from Dynamic part.`. This means...