#Unresolved External Symbol despite including header

46 messages ยท Page 1 of 1 (latest)

dusky mulchBOT
#

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.

manic jay
#

!howto ask

dusky mulchBOT
# manic jay !howto ask
How to Ask A Programming Question

Anyone can ask a question in our programming channels. Following the guide Writing The Perfect Question is recommended.

What To Post

State your problem clearly and provide all necessary details:

  • the relevant portion of your code, or all of it
  • the expected output
  • the actual output (or the full error) ๐Ÿ† Gold Standard: Minimal Reproducible Example
Where To Post

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:

  • Compiler Explorer for most C/C++ snippets
  • OnlineGDB for interaction, debugging โ›” Do not post screenshots, let alone photos of your screen!
left heath
#

๐Ÿ–•

#

!close

dusky mulchBOT
#

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 Do Not Delete Posts!

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.

left heath
#

!solved

dusky mulchBOT
#

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

manic jay
#

Rude :/

left heath
#

well idk what to share without sharing 100s of lines so

main plaza
#

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

left heath
#

again relevant parts being a ridiculous amount because errors are everywhere suddenly

main plaza
#

@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

left heath
#

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

main plaza
#

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

left heath
#

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

main plaza
#

Please click on the output tab

left heath
#

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.

main plaza
#

Perfect

#

Do you know how to resolve this error?

left heath
#

string was already included

#

which is how that type of issue is normally resolved

#

something is just very, very wrong and idk why

main plaza
#

!cppref string_view

dusky mulchBOT
left heath
#

Really? I've literally always used #include <string> for string_view and it has always worked

#

im using MSVC if it means anything

#

and it was working before my power went out (that error specifically)

main plaza
#

It's entirely implementation defined what headers might include what other headers. But never rely on it.

#

Sometimes headers can include partial declarations for things

#

So thing can seem to work but break later.