Adam Welc

We were admittedly rather tied up with the mainnet launch until recently, but it's time to get back to enhancing the IDE! I was wondering if there is any progress...

> we are still working on that, will keep you posted Do you have some kind of timeline in mind that you could share?

> Okay, just one final question from me, about how we handle overrides in the case where the package table is vacant at the entry for that overridden package, and...

The enhancements in this PR look very useful, thanks! It looks like you went the route some other language analyzers followed which is to re-implement the front-end portion of the...

> Can we take over the maintenance of the Move Analyzer? In principle, we like this idea, but we need to figure out if we can work it out at...

@robinlzw - it would also be good to know how you see maintaining the original Move Plugin on your side. In particular, at this point there are two VSCode marketplace...

> we need to figure out if we can work it out at a technical level We tried to see if this would be possible but the consensus among the...

Converted to draft as apparently exposing this is a big no-no...

Modified custom memory support to remove custom memory naming and bringing back quant translation at the cost of adding an additional builtin to expose user-defined Boogie-level global variables. This allows...

Overrides are specified explicitly, rather than what the previous solution assumed, that is implicitly. In other words to override some dependency `C` that `A` and `B` depend on (and conflict...