Update troubleshooting guide #319
Merged
Conversation
This file contains 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
The biggest change is that we add a new section for the new kind of error, when users try to pass something to a `QuantityMaker` even though it's already a `Quantity` (and similar for `QuantityPoint`). We also update the guidance to recommend `unblock_int_div` instead of the obsolete `integer_quotient`. Other than that, the PR basically consists of running the build under the five configurations shown here, and copy-pasting error messages. Most changes are just line number tweaks. Some changed implementation details do show up in the error messages. Also, sometimes the compiler changed to be more or less verbose. The details of the changes aren't really important (assuming that I copy-pasted correctly). It's just an update. Fixes #288.
chiphogg
added
the
release notes: 📝 documentation
geoffviola
approved these changes
Oct 31, 2024
| D:\a\au\au\au.hh(2334): error C2338: Elements must be listed in ascending order | ||
| error_examples.cc(113): note: see reference to function template instantiation 'bool au::operator ==<au::Quarterfeet,au::Trinches,int,int>(au::Quantity<au::Quarterfeet,int>,au::Quantity<au::Trinches,int>)' being compiled | ||
| D:\a\au\au\au.hh(3132): error C2338: Elements must be listed in ascending order | ||
| D:\a\au\au\au.hh(1310): note: see reference to class template instantiation 'au::CommonUnit<T,au::Quarterfeet>' being compiled |
There was a problem hiding this comment.
It's a little surprising this error got longer.
There was a problem hiding this comment.
Yeah, I thought so too.
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.
The biggest change is that we add a new section for the new kind of
error, when users try to pass something to a
QuantityMakereven thoughit's already a
Quantity(and similar forQuantityPoint).We also update the guidance to recommend
unblock_int_divinstead ofthe obsolete
integer_quotient.Other than that, the PR basically consists of running the build under
the five configurations shown here, and copy-pasting error messages.
Most changes are just line number tweaks. Some changed implementation
details do show up in the error messages. Also, sometimes the compiler
changed to be more or less verbose.
The details of the changes aren't really important (assuming that I
copy-pasted correctly). It's just an update.
Fixes #288.