David Piepgrass

> I don't know of any fundamental reason why custom literals should always be represented by strings They are not always represented by strings. > custom literals and type markers...

I'm tweaking the precedence of `->` and ``, etc.) but I don't really see why they should be. I also made these oeprators right-associative. So `c && a 1` will...

Oh, and I'm changing them to be right-associative.

One more thing, I notice that four-char codes like "\u2022" are valid JSON but larger code points like "\u1F4A9" and "\u01F4A9" (💩) don't work; only the first four characters contribute...

I just realized this isn't (always) a satisfying answer for dictionaries. Today I added a class called `SelectDictionaryFromKeys` for adapting the interface of a dictionary on the fly (`AsReadOnlyDictionary` extension...

Plan B: don't remove support IList and ICollection extension methods outright, but put them in another namespace so they don't cause "ambiguity" every time I want to use an extension...

I've committed some changes in this direction, mostly moving extension methods on ICollection and IList to a new namespace called `Loyc.Collections.MutableListExtensionMethods`. TODO: after dropping support for .NET 3.5/4, do another...

Okay, I just released a .NET Standard version. And I agree, LES is great for DSLs and that would be better marketing than "an interchange format for syntax trees". I...

New spring cleaning item: #84 - I might do this right away, or I might wait a year, haven't decided.

New spring cleaning item: consider eliminating `StringSlice`, replacing all uses with `UString`. Update: done!