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
hkaiser has quit [Read error: Connection reset by peer]
hkaiser has joined #ste||ar
hkaiser has quit [Quit: Bye!]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo1 is now known as K-ballo
Yorlik_ has joined #ste||ar
Yorlik_ has quit [Read error: Connection reset by peer]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 244 seconds]
K-ballo1 is now known as K-ballo
hkaiser has joined #ste||ar
hkaiser has quit [Quit: Bye!]
hkaiser has joined #ste||ar
hkaiser_ has joined #ste||ar
hkaiser has quit [Ping timeout: 264 seconds]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 255 seconds]
K-ballo1 has quit [Ping timeout: 276 seconds]
K-ballo has joined #ste||ar
ms[m] has joined #ste||ar
hkaiser_ has quit [Quit: Bye!]
<gonidelis[m]>
We have a new guy on the block, Carbon
hkaiser has joined #ste||ar
<satacker[m]>
It’s C
<satacker[m]>
XD
<gonidelis[m]>
shots fired!
<gonidelis[m]>
just waiting for K-ballo: 's take
<hkaiser>
gonidelis[m]: I find it to be an unfortunate mix of rust, go, and perhaps some swift
<hkaiser>
it does not deliver on the most important thing: having no undefined behavior by default, i.e. being safe by default
<gonidelis[m]>
people keep trying to reinvent the wheel smh. just fix the damn Car
<hkaiser>
NIH all over again
<gonidelis[m]>
yup, people love lack of safety
<K-ballo>
if it turns out to be what swift is to objc and kotlin is to java it will be most welcome
<K-ballo>
same underlying engine, machinery, etc.. 100% compatible.. without all the legacy cruft
<K-ballo>
to early to tell
diehlpk has joined #ste||ar
diehlpk1 has joined #ste||ar
<hkaiser>
K-ballo: in principle yes, I'm not happy that they still go with having undefined behavior
<hkaiser>
the 100% back&forth compatibility with C++ however is great (and an absolute must)
<hkaiser>
the syntax of the language is secondary in the end, as long as the sematics are right
diehlpk has quit [Ping timeout: 244 seconds]
diehlpk1 has quit [Quit: Leaving.]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 276 seconds]
K-ballo1 is now known as K-ballo
diehlpk has joined #ste||ar
<K-ballo>
syntax is only secondary to some extent, remember the days of algorithms without lambdas
<hkaiser>
K-ballo: agreed
<hkaiser>
as said, as long as the semantics are right I don't care about the syntax
diehlpk has quit [Quit: Leaving.]
diehlpk has joined #ste||ar
diehlpk has quit [Client Quit]
diehlpk has joined #ste||ar
diehlpk has quit [Client Quit]
<gonidelis[m]>
does `std::visit` on two variants require for every combination of the Cartesian product of the types of the variants to be invocable with the function provided?
<gonidelis[m]>
i thought it was a switch (say if the combination of these two types can be called with this function, I ll do it, else I skip it)
<hkaiser>
gonidelis[m]: yes
<gonidelis[m]>
that does not sound like a switch
<gonidelis[m]>
more like a for
<gonidelis[m]>
foreach
diehlpk has joined #ste||ar
diehlpk has quit [Client Quit]
diehlpk has joined #ste||ar
diehlpk has quit [Quit: Leaving.]
diehlpk has joined #ste||ar
diehlpk has quit [Client Quit]
diehlpk has joined #ste||ar
diehlpk has quit [Client Quit]
diehlpk has joined #ste||ar
<hkaiser>
gonidelis[m]: you can always have a fully templatized overload in the mix that will be used as a fallback
Yorlik has joined #ste||ar
<gonidelis[m]>
why have std::apply when you have std::invoke?