Brice
The whitespace rules are more reasonable and less surprising with the new parser in 2.1.
Adding a note to mention that we may want to add a new, separate cost function for parsing with the v2 parser, as it is significantly cheaper than the original...
This will be caught and reported as an error by the new parser.
The new parser catches and reports an error when a contract principal in the code has a contract name longer than 40 characters - see https://github.com/stacks-network/stacks-blockchain/blob/3a24af692776c822f0ddb238c9362d09c6f6d12d/clarity/src/vm/ast/parser/v2/mod.rs#L2782-L2801 The parser can't do...
I'll rebase and fix this conflict, then request new reviews.
@jcnelson @lgalabru any open issues here or can we get this one merged?
> Before merging, let's make sure `integration_test_get_info` works. It seems this is still failing. I'm not familiar with these integration tests yet, or even how to run them locally. Can...
Ok, that error is solved and this PR should be good to go now!
The [new parser](https://github.com/stacks-network/stacks-blockchain/pull/3150) will improve on some of these items already. It should solve all of the whitespace issues for example.
Yes, definitely agree on that point.