Jonathan Lindegaard Starup
Jonathan Lindegaard Starup
Oh, actually the same solution. In conclusion, this changes make the verifier run for very little code size (conjectured)
I think i was convinced by matts solution - the things that conceptually return an iterator instead return an IterableFactory. It seems like a very flexible and generic solution to...
These are just specializations of `Int64.clampToInt32(min: { min = Int32 }, max: { max = Int32 }, x: Int64): Int32` fx right? I think just having the version with default...
> I needed something that corresponded to Java casting exactly Oh right, clamp is different. But still we could have `Int64.chopToInt32` that uses modulo and things, we don't need the...
I don't remember changing or implementing it. Shouldn't native operations be native, no matter the zero crash case?
@magnus-madsen its assigned to me but also marked student programmer. Should I work on it?
Subsumed by #7409
The constructed toString would break like #7181
> @JonathanStarup Remember: The verifier does not have to be perfect. It is just intended for us (and students) to quick catch stupid errors. But you also want to make...
It is conceptually impossible