Joe ST
Joe ST
is there a reason (that I'm not seeing) that this cannot be done with a macro that just implements the wrapping functions in a generated `impl` block?
is it worth explicitly mentioning in the Experiment section that "burnout"/etc of the Responsible Party is a totally valid reason for closing the experiment? similarly is there an upper limit...
reading through this I don't see why it isn't the same as `'_` in all the explanations
if they can't be negated then that should possibly be mentioned, (unless the error message is great?) or if there _is_ a better example that can be added later then...
that would be awesome, +1
I see there is no mention of [pattern types](https://github.com/rust-lang/rust/pull/120131) though it seems they would be similar but distinct use of `is` as an operator? is this a pre-requisite of pattern...
would be good to have a `/events?year=2014` route to filter the event list to a single year
my desire for the year parameter was when arcanizing the coppermind I would often know the date of the entry but not the event nor the "exact text" enough to...
also maybe show a daily/random entry on the homepage/sidebar?
that still requires you to input the correct date range manually, rather than a simpler selector