David Piepgrass

JSStats seems interested in making sure that wasm modules can contain rich metadata, and he is prepared to build something on top of the official wasm spec if the core...

~~~ Console.ReadLine() |> File.ReadAllBytes() |> SHA1.Create().ComputeHash() |> BitConverter.ToString() |> Console.WriteLine("SHA1: {0}"); ~~~ So that's supposed to mean this? ~~~ Console.WriteLine("SHA1: {0}", BitConverter.ToString( SHA1.Create().ComputeHash( File.ReadAllBytes( Console.ReadLine())))); ~~~ I'm not sure how...

By the way, when you used `Do()` in your comment, I suppose you meant a method like this? public static R Do(this T obj, Func action) => action(obj); It's funny...

I guess you mean `To` as a synonym of `Do` and I guess `par` means "parallel" but I don't understand the intended semantics of `@::`, or `par { x }`,...

I don't think it's worth a new operator when you can just write `(await A())::a != null`... though personally I never had to use async extensively.

How about this. Define the following macro: define operator.($x, awaited) { (await($x)); } (The parentheses are requires around `$x` because the `await` operator does not exist outside `async` functions, but...

Yes, you can. And, fun fact, `define` is unaware of operators... in EC#, `operator/` is just a function name like any other. In Loyc trees, operators and functions and constructs...

While I added `|>` and `?|>` operators in 2.8.3, I didn't actually implement a macro to transform them. And there isn't a mechanism yet to write "smart" macros (i.e. macros...

In the latest commit, you can define macros in C# code using a new `macro` macro. Exciting times! ~~~cs ["Change first argument to HELLO if it's not an identifier", Passive]...

Okay, I still haven't actually released v29, but I will soon, and `compileTime {}` is now able to map error locations back from the plain C# code to the original...