-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@u_str macro hygiene? #272
Comments
This is a consequence of the way that Perhaps we could do better, but for now the workaround for this is to make sure there's a binding for using Unitful: Unitful, @u_str |
c42f
added a commit
to c42f/Unitful.jl
that referenced
this issue
Jan 17, 2020
Generalize the handling of `@u_str` and the unit extension module context to allow the same machinery to be used for a new `parseunit` function which does the same thing at runtime. Fixes PainterQubits#272 as a side effect of generalizing `@u_str`.
ajkeller34
pushed a commit
that referenced
this issue
Jan 25, 2020
* Parsing of units from strings Generalize the handling of `@u_str` and the unit extension module context to allow the same machinery to be used for a new `parseunit` function which does the same thing at runtime. Fixes #272 as a side effect of generalizing `@u_str`. * Rename parseunits -> uparse Also add a test for #272 * Make unit_context a keyword
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure if this is intentional or not, but I expected it to be sufficient to just
import Unitful: @u_str
in order to use e.g. u"m".The text was updated successfully, but these errors were encountered: