Pietro Vertechi

Thanks for the notification! I imagine (correct me if I'm wrong) that at this point, this project is primarily a "conversion layer" between the Wiktionary API and the free dictionary...

I can confirm the issue. I followed the same steps as @salvoc81 but on [this repo](https://gitlab.com/VeosDigital/KernelMachines.jl) and got the same "unable to fetch repository" error.

In terms of API, I was thinking that one could pass the values in the cotangent on which to accumulate the `pullback`. So for example, for a function ```julia z...

I've commented over at https://github.com/JuliaArrays/StructArrays.jl/issues/126#issuecomment-624011508. It can be made to work already if one calls the constructor in a slightly different way, and one gets a ```julia StructArray(data::StructArray(::Array{Float32,1}, ::Array{Float32,1}, ::Array{Float32,1}))...

Came here from https://github.com/JuliaArrays/StructArrays.jl/issues/135 (cc: @Sov-trotter ) I'm slowly wrapping my head around this use case. I am slowly realizing that what I said there may be a bit misleading,...

The only tricky thing is that widening over a custom type is a bit ill-defined, as in general it's impossible to know how the parameters should change. The first step...

I also feel that the `Meta` approach is a bit extreme, and something like your `Feature` could be safer. Normally, if you want to create a new `StructArray` with the...

@SimonDanisch was commenting (in a separate discussion) that in his experience generated functions can actually be faster to compile than the non-generated counterpart and was afraid that this could slow...

That's a good point, I see why `push!` and `pop!` are problematic because of the iteration order. Slightly off-topic, but I ended up wanting to use `pop!` (well, rather `delete!`...

I've also noticed this issue and, while it's true that fixing it for `Iterators.map` is a bit tricky (because of the type parameters of the lazy mapped dictionary), I was...