Darren Duncan

For any collection type that is supposed to be able to have elements of any type at all, it seems a very poor design decision to have a special value...

> @duncand Raku has [`:exists`](https://docs.raku.org/language/subscripts#index-entry-:exists_(subscript_adverb)), [`.EXISTS-KEY`](https://docs.raku.org/routine/EXISTS-KEY) and [`nqp::existskey`](https://github.com/Raku/nqp/blob/master/docs/ops.markdown#existskey). > > @duncand This is about the very low level **implementation** in Rakudo. Nothing to do with design. I suggest you familiarize...

I have also noticed in the past that CQL Runner sometimes doesn't display a subset of the define outputs at all, they just aren't mentioned. I suspect this specific issue...

> 1. They are severely impractical. Giving something a name that is neither descriptive, nor properly searchable doesn't seem to be justified by the amount of fun they give to...

> * On `Dateish` specifically: In theory, I like the idea of `ish` as a role marker – the problem is that Raku uses `y` as the role marker elsewhere:...

> As to `Positional`, `Associative`. Let's be consistent and use `Listy`... `Listish`??? Eh... Thanks, no! ;) Nonsense! The `Positional` and `Associative` are the most optimal kinds of roles which are...

> > On naming, the way one distinguishes a class from a role is by the grammatical category of the word, NOT its spelling. A class has a NOUN as...

> the BOM is because, when it is omitted, many diff tools incorrectly guess the encoding. if we add an option to omit it, other people will hit the encoding...

> I'd also suggest the defaults be UTF8 _without_ BOM, and always a newline at the end of the file. But that's just my preference. Those are also my personal...

Targeting .NET Standard 2.0 where possible will provide the best cross-platform support for those components, with respect to being able to run on all major operating systems including .NET Core...