When your question is answered use !solved to mark the question as resolved.
Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question run !howto ask.
46 messages ยท Page 1 of 1 (latest)
When your question is answered use !solved to mark the question as resolved.
Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question run !howto ask.
!howto ask
Anyone can ask a question in our programming channels. Following the guide Writing The Perfect Question is recommended.
State your problem clearly and provide all necessary details:
Provide the relevant code in the message, and format it nicely with a code block*. If it's too much for one message, you can upload it:
Thank you and let us know if you have any more questions!
This thread is now set to auto-hide after an hour of inactivity
@left heath
Please don't delete forum posts. They can be helpful to refer to later and other members can learn from them. In the future you can use !solved to close a post and mark a post as solved.
!solved
Thank you and let us know if you have any more questions!
This thread is now set to auto-hide after an hour of inactivity
Rude :/
well idk what to share without sharing 100s of lines so
Please don't be rude to people trying to help
That guide, if you read it, will tell you how to ask a programming question and what information to share
I.e., the relevant parts of your code and what you've tried and what issues you are running into
again relevant parts being a ridiculous amount because errors are everywhere suddenly
@left heath Always start with the first error.
The first error from the compiler is the only one you should trust (until you know what to look for), everything else can be a red herring
Everything was fine until it wasn't. I changed one thing and 100+ errors flooded in and didn't know why. It is not as simple as starting with the first error because they all resulted as a result of one change.
I made progress and the first error was not relevant to the solution, so thanks
Syntax errors tend to snowball
So start with the first one
Click on the output tab in vs rather than the error tab
Send the first error and the relevant code
Nothing like these ones appearing only after my power went out
I'm so confused. I almost had it fixed. Power went out and now my entire project is in FLAMES
3,920 warnings
Please click on the output tab
First thing in output tab, you got it
error C2039: 'string_view': is not a member of 'std'
and this error only appeared after my power went out.
string was already included
which is how that type of issue is normally resolved
something is just very, very wrong and idk why
You need to include <string_view>
!cppref string_view
template<
class CharT,
class Traits = std::char_traits<CharT> >
class basic_string_view;