Jacek Generowicz

Apologies, I should have stated explicitly that it was obvious to me (so obvious, apparently, that it didn't seem worth mentioning) that Kinds were getting in the way, and why...

Thanks. Good point about zero-weight-sum. Yes, intended the `Option` to guard against zero-length input. For my needs, zero-sum-weights should probably panic but I need to think about it a bit...

Apologies for the long delay, my time to work on this is sporadic. I agree, the code duplication is quite horrendous. When I try to make sense of it, I...

So you can think of the whole recursive macro invocation graph as a tree, with macro invocations at the nodes, and actual code (`impl`s) as the leaves. I think that...

Could you help me make sense of the existing implementations? Looking at the original code, I see the following nine `impl`s: | | lines | ops | | autoconv |...

Are there any difficulties or pitfalls here, or is it just a fairly mechanical process that simply requires finding the time to do it? If it's the latter, I'll start...

> Implementation would start with the following macros [`impl_ops!`] Just to be sure: Are you suggesting to add the implementations of the reference versions, to the bodies of those macros?...

Another related problem arises in the context of #289: > Do you see use for affine/vector quantities beyond length? Are there cases in your simulation where Point and Vector are...

Thank you so much! This is very useful. > `type PerQuantity = Quantity;` I think you meant: ```rust type PerQuantity = Quantity; ``` > If you have started implementation and...

> too many changes in the test project and I missed copying over to my reply. Probably worth editing it, for the sake of future readers. As it stands, `PerQuantity`...