Enhancement: proper compile time errors (WIP)#30
Open
IkerGalardi wants to merge 1 commit into
Open
Conversation
Owner
Author
|
Don't think there is a better way than this. Still, better than what we have now, so we can merge to main this PR (when completed) and when we discover something as fancy as the |
Owner
Author
|
If issue #35 gets implemented it would be much easier to implement it as all the implementations would be centralized. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Using the
static_assertcompile time checking custom messages can be sent. Using that, still, lots of template error stuff is thrown.If there was a way to just print the line in which the error is thrown and the custom message, that would be much nicer than the current error stack.
This issue tries to solve the issue #26 .