Kunal Sareen

I have a commit here https://github.com/k-sareen/mmtk-core/commit/d12fe11c886e8bdad988d61bc4e6450515f0db6e which does the same but allows MarkSweepSpace to either be malloc or native-based. But I'm not sure if using malloc MS is worth it.

I've been reading the type checking code in `vst/Verifier.v3` and I don't understand why the `ve.expr` has to be `null`, i.e. why the match case has to be the unqualified...

For the error generated by `test/fail/adt_type_infer03.v3` (in PR), I think the [`TypeSystem.isPromotable()`](https://github.com/titzer/virgil/blob/e8079d6356f28115954ab5425334d4e6c848a8d1/aeneas/src/v3/TypeSystem.v3#L75-L94) should return `true` because, well `A.C` and `A.C` are the exact same type. Unless is there some internal...

> I'm open to designing such a mechanism. One question is what to do with functions/APIs that take Pointer. Technically, the unsafe things being done (like Pointer.atContents, etc) happen in...

Yes that makes sense. Sorry for being AWOL again -- just have too many deadlines. Will be more free after mid-April. Might try my hand at making an LSP server...

> My concern is how much real code will end up with ? everywhere for nullable types Yeah. In my subjective experience with Rust, it can litter the code with...

Though Virgil already has a lot of: ``` val = something(); if (val == null) { fail("val is null"); } ``` which would be cleaned up by the `?` operator....

Yes that makes sense to me. What do you imagine the semantics of a nullable type are? For the sake of argument, let's take a user defined type `Foo` that...

> I think an error for accessing fields or calling methods on a nullable type would be in order. (Otherwise, what's the point, ja?) Haha yes of course. I meant...

> Perhaps. One thing about errors that I have dealt with a lot recently is that the error cases basically have arguments, such as which file or line number they...