hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
K-ballo has quit [Quit: K-ballo]
hkaiser has quit [Quit: Bye!]
jehelset has joined #ste||ar
Yorlik has joined #ste||ar
ruchipakhle has joined #ste||ar
ruchipakhle has quit [Quit: Client closed]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
<K-ballo>
hkaiser: did they give you an ETA for the letter?
<hkaiser>
K-ballo: no, I just put it in the mail last week Tuesday
<hkaiser>
or was it this week's Tuesday ? :/
<hkaiser>
time flies
jehelset has quit [Ping timeout: 260 seconds]
jedi18[m] has quit [Quit: You have been kicked for being idle]
jehelset has joined #ste||ar
jehelset has quit [Remote host closed the connection]
<Yorlik>
I am trying to hide away some implementation details with a nested "detail" namespace. But suddenly the symbols do not get found anymore, even if I prefix them with detail:: . What am I missing here?
<Yorlik>
NVM - some forward declares exploded ...
<Yorlik>
Do I understand this example right, that search order in nested namespaces is always from inner to outer? https://godbolt.org/z/j4Ker9Wos
<K-ballo>
I don't understand the example
<K-ballo>
ordinary lookup does look in the current namespace first, if it doesn't find anything checks the outer namespace, and so on until the global one
<K-ballo>
I suppose the example shows somestruct in line 15 refers to the one from line 9?
<Yorlik>
The two somestructs have different members. And it seems the compiler took the one in the B namespace. trying to write to a member of the somestruct in the A namespace resulted in an error. So I guessed it went from inside to the outside.
<Yorlik>
So - what you say basically confirms that.