Psilon

@eggplantzzz hmm, I'm sorry, I was sure it was an intended API which is quite useful when you have contract name clashes, so you can manually resolve which exact contract...

I did my small research on github and I didn't actually find any use cases where ability to serialize `[T; 0]` would be beneficial. A couple of points: 1. If...

Fantastic PR. Can we please have any word from the maintainers on this?

@MgSam it's easy to write and hard to read. As you know, 80% of time you are reading the code. Thus this should be never get implemented.

@AlenPelin it's looks like curing the headash by heading yourself... Traling comma looks like empty statement which is pretty valid and which is the source of great amount of bugs....

@AlenPelin you already have several options: 1. Start new line with commas just like with dots. No one cares about LINQ because most of queries are written in `dots first`...

most of use cases of `var` are anonymous types or very long names like `IGrouping` and so on. There is no problem with writing `const int` or `const string` especially...

@CyrusNajmabadi this feature is as simple as implement `_` to be a separator in numbers, but it just doesn't provide any expressiveness. @jnm2 it's quite common to explicitly specify simple...

Interesting fact: Rust has `let` statement with optional type ascription for anything *but* constants, where it's required.

Note that Mac ChezCheme PR was merged; see https://github.com/cisco/ChezScheme/issues/545#issuecomment-1768915042 This now can be done I suppose