Sebastian Stock

@Eben60 Yes, I can apply these changes myself. No problem!

I wouldn’t say the value is *wrong*, the quantity is just accidentally given in "unusual units". You can convert it to SI units and get the correct value: ```julia julia>...

I am reopening this so that we don’t forget to change it (I think it should be changed).

Thanks for your contribution! I think it would be good to add the new prefixes, but there is one aspect to consider: `Unitful.rm` (rontometre) will collide with `Base.rm` (function for...

The test failures on master are unrelated (they are fixed by #689, which was merged after this PR was posted).

> 1 default value of unit_context argument IMO, this is a good change. > 2 allowed_funcs > To enable parsing some strings such as "(1:10)m", I added `:colon` and `:(:)`....

`u` is a unit of *mass* and `g/mol` is a unit of *molar mass*. These are different dimensions, so one cannot be converted to the other. Also, since [20 May...

This will also apply to ranges, which makes it different from the current behavior: Before: ```julia julia> r = (1:5)u"m" (1:5) m julia> ustrip(r) 1:1:5 ``` After: ```julia julia> r...

> how about redefining `ustrip(::Array...` to dispatch on `DenseArray` instead I like that. Maybe we could even use `StridedArray` instead of `DenseArray`, which is more general and still makes sense....

I just noticed that this is technically a breaking change. At least I consider it as one. A user that calls `ustrip(view(…))` in their code may now unintentionally modify the...