Adam Welc

OK, I was actually thinking of introducing the version number to all Move.toml files, so that we have a mechanism to warn developers of some changes that might otherwise go...

OK, I think I need some advice from those who possibly thought this through more thoroughly, as it seems to me that implementing the proposal in the current form is...

> I think it should be easy to get the information with some small changes to the package system. That's really the kind of feedback I was hoping for. I...

> Alternate thought that requires no changes to the package system: Hash the source files and then check the hash? Smart! This could be a bit noisy, though, as ANY...

On the other hand, thinking about it a bit more, people really shouldn't use a version of framework code incompatible with the binary they use to build their apps, so...

My apologies, this completely slipped off my radar. We had internal discussions about auto-formatting and none of the existing solutions is mature enough to be made an "official" one. The...

As far as I know one of the main problems with full-fledged auto-formatting is deciding where and how to split lines when they get too long. I don't think a...

> @awelc @zsluedem I think I want give the `TokenTree` a try. On our side we normally prefer re-using (and modifying if necessary) the existing tool chain rather than building...

> Thanks @awelc ! I've added a Jira for myself to add this topic to the navigation, too. I have accepted all the suggested changes but will wait for @amnn's...

Modified this PR to match updated support on the core Prover side (https://github.com/move-language/move/pull/810). In short, we can now re-use global mapping from the core Prover as well as define (and...