-
Notifications
You must be signed in to change notification settings - Fork 18
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 type constructor on default from_string #96
Comments
rfernandes
added a commit
to rfernandes/toolbox-cpp
that referenced
this issue
Jun 18, 2020
The common case of TypeTraits::from_string should use the target type's constructor, this removes the need to specialize it for those that support String-type constructors, ex: Path. Removing Path files also removes the last "experimental" header Closes reactivemarkets#96
rfernandes
added a commit
to rfernandes/toolbox-cpp
that referenced
this issue
Jun 18, 2020
The common case of TypeTraits::from_string should use the target type's constructor, this removes the need to specialize it for those that support String-type constructors, ex: Path. Removing Path files also removes the last "experimental" header Closes reactivemarkets#96
rfernandes
added a commit
to rfernandes/toolbox-cpp
that referenced
this issue
Jun 18, 2020
The common case of TypeTraits::from_string should use the target type's constructor, this removes the need to specialize it for those that support String-type constructors, ex: Path. Removing Path files also removes the last "experimental" header Closes reactivemarkets#96
markaylett
pushed a commit
that referenced
this issue
Jun 18, 2020
The common case of TypeTraits::from_string should use the target type's constructor, this removes the need to specialize it for those that support String-type constructors, ex: Path. Removing Path files also removes the last "experimental" header Closes #96
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The common case of TypeTraits::from_string should use the target type's constructor, this removes the need to specialize it for those that support String-type constructors, ex: Path.
The text was updated successfully, but these errors were encountered: