On Sat, Oct 31, 2020, at 5:06 AM, Rowan Tommins wrote:
> > This would be
> >an artificial limitation on attributes to patch over the inherent
> >inconsistency of the grouped syntax for nested attributes.
>
>
> There is no artificial limitation; there is a binary choice: does
> #[Foo] represent
@Levi
> However, I still see CPU related code in get_cpu_features. Are you
> sure you pushed the right thing?
I think it's correct, yes, the problem is ext/hash/blake3/blake3_dispatch.c,
which is just a copypaste of the upstream
https://github.com/BLAKE3-team/BLAKE3/blob/master/c/blake3_dispatch.
On 30 October 2020 21:54:10 GMT+00:00, Theodore Brown
wrote:
>The fundamental advantage of using an attribute here instead of an
>associative array is that it enables IDE autocompletion, and allows
>static analyzers to catch any mistakes in the parameter names/types
>before the code runs in produ
