Claire Foster

BTW, I'm continuing to love the simple composable design of this and related packages. At this stage it just needs good documentation to clearly show how nice it all is!

Thoughts on the next section # Basic data manipulation ## Mapping rows of data ### Using map Extracting a column - perhaps too simplistic given that there's another much better...

Next section... one thing which strikes me here is that you're not really documenting TypedTables per se? But the Andyverse of data analysis? Which makes it kind of odd that...

Random (likely useless) thought bubble — having just written that AcceleratedArrays is great because it decouples performance from query semantics — could we think of the types in `Table` in...

> Should we define decellerate(t::Table) = FlexTable(t)? Not *quite* what I was thinking :-) More like trying to define ```julia const FlexTable{N} = Table{Placeholder, N, NamedTuple{

:100: That's a really interesting article for framing the discussion around documentation. It's very interesting that they insist that these four types of documentation are really separate and should be...

Yeah the explanation of a design is hard to write and make useful. The abstract design arises from a bunch of concrete use cases and practical constraints... but writing those...

Oops, got the link wrong... [here's](http://sci-hub.tw/10.1109/SYSCON.2018.8369508) the paper which talks about using category theory for Formal Design.

I do wonder whether `_.name` will get into 1.1. The issue of binding tightness is really thorny. Reading back on the issue, I'm rather dissatisfied with tight binding and Stefan's...

Well, you totally nerd sniped me with the underscores business... Now there's [MagicUnderscores.jl](https://github.com/c42f/MagicUnderscores.jl). You're the first to see it :-P