Andy Dienes
Andy Dienes
in case the reference is useful, dropping the link to the `polars` meta-issue for aggregations of datetime-like types https://github.com/pola-rs/polars/issues/13599
are non-trivial inf loops UB?
> const replacement is definitely full on UB IMO anything that is * easily detectable * "full on UB" should error, rather than warn? maybe also applies to the `a...
I would suggest that one of the individual options should be disallowing control flow in non-"statement" position, i.e. https://github.com/JuliaLang/julia/issues/50415
this is in the appropriate NEWS and HISTORY now
I suggest re-closing this as https://github.com/JuliaLang/julia/issues/11339 is already an issue for distinguishing specialization and dispatch, but I don't want to override keno
please, no I think `Missing` should stay in its statistics corner and only propagate in statistical contexts Imo it already propagates through far too many functions.
wait, why does `missing` work with `∘` in the first place? it's not a function I'd sooner special case an error path for `∘(::Missing)` than make it propagate.
unary `+` means that's failing for the same reason as ``` julia> [a b for i=1:1] ERROR: ParseError: ``` I would call this a dup of https://github.com/JuliaLang/julia/issues/30464 or https://github.com/JuliaLang/julia/issues/27881 (which...
fixed in 1.12