Maksim Volkau

@qwertie Thanks for release! > Are they really adding top-level statements to the main language (not C# interactive)? Yes.. and while it is a bonus feature, honestly I would like...

> I've always thought that the build system should be based on the same syntax as the programming language itself... this makes the most sense if the syntax is very...

> What EC#/LeMP really needs is more and better tooling, I think. Not having IntelliSense is a pretty big limitation, among other things. But, I kind of need a stronger...

> By the way, when you used Do() in your comment, I suppose you meant a method like this? Yeah I have such `Do` too. Over the years I am...

@qwertie ...and while we are at it, your glorious postfix `::` operator give me an idea of how to tackle the monadic "do-notation" in more ergonomic way than C# Linq...

> ?|> where A ?|> B(...#...) means A::tmp == null ? null : B(...tmp...) Yes, that's what I mean. For now please ignore the rest - sorry for the bloat...

The `async` and `await` is used extensively in (micro)Service, API, and LOB apps.. So the method lengths there are big like this: ```cs await _powerUsersMongoRepo.GetAllUnderpoweredUsersByIds(blahhhhhhhh).ToList(); ``` Here is the error...

> How about this. Define the following macro... Will try it out! But that's opening a lot of possibilities. I presume I can use other operators as well.

> define operator.($x, awaited) { (await($x)); } Here is more foundation and discussions for the thing: - https://github.com/dotnet/csharplang/issues/1117 - https://github.com/dotnet/csharplang/issues/35

@qwertie Anyway, this is cool and something I can start using (even if to learn more about complex lemp stuff). Also, means that the tool is mature enough to provide...