-
Notifications
You must be signed in to change notification settings - Fork 44
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
Use a less generic user-defined literal #38
Comments
I acknowledge that this problem is a pain. You can also use |
I'd definitely prefer the UDL over the macro. The macro feels like a significant step backwards considering how cutting edge this library is. Seeing as the macro actually has similar namespacing issues (worse, of course, due to the global namespace pollution not being opt-in) which are solved with a C-style |
Would you suggest the I've made the change of |
no because if the UDL is defined inside only the i don't think |
Due to issues with using user-defined literals without exposing the whole namespace and interfaces generally being defined in a header, it's pretty much required to release
dyno::literals
into your own namespace. The problem here is that_s
is far too generic, could the user-defined literal be_dyno
?The text was updated successfully, but these errors were encountered: