Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Mar 03 2017 15:52
    @dom96 banned @Octopoda7
  • Feb 12 2017 23:57
    @dom96 banned @zzz125
  • Dec 23 2016 19:43
    @dom96 banned @Izrab
From IRC (bridge bot)
@FromIRC
<leorize[m]> @Elegant Beef: that's pretty much expected
<FromDiscord> <Elegant Beef> That was more of a joke then anything
Kaushal Modi
@kaushalmodi
Araq: I never used nimgrep because I am comfortable with sed and rg
From IRC (bridge bot)
@FromIRC
<FromDiscord> <Elegant Beef> Not like i have a very viable test of this ecs considering i lack something to run it in
Kaushal Modi
@kaushalmodi
will have a look at that soon
From IRC (bridge bot)
@FromIRC
<FromDiscord> <Elegant Beef> So for the components, i think using a macro to make them makes more sense but idk
<disruptek> probably, yeah.
<FromDiscord> <treeform> Araq, wow GTK + SDL + your app is only 20MB?
Kaushal Modi
@kaushalmodi
leorize: So when would one use just .exportc.?
If the symbol doesn't get exported when just that pragma is used, when what's the point?
s/when/then
From IRC (bridge bot)
@FromIRC
<leorize[m]> I do know an use case for the compiler codegen
Kaushal Modi
@kaushalmodi
ok (that's out of my reach then :) )
From IRC (bridge bot)
@FromIRC
<leorize[m]> compiler procs are exportc-ed then called via codegen by inlining the exported name
<FromDiscord> <treeform> Araq, Nimx is also 35mb...
<FromDiscord> <treeform> I need to figure out how to get it to only 20mb.
<FromDiscord> <treeform> get my thing*
<disruptek> treeform: how does this 35mb compare to other nim guis?
Kaushal Modi
@kaushalmodi
leorize[m]: I couldn't help think.. shouldn't exportc implicitly do dynlib too?
for the few cases where that should not happen, that's where you require a second pragma
now I have a huge diff of 200+ changes that changes {.exportc.} to {.exportc, dynlib.}
From IRC (bridge bot)
@FromIRC
<disruptek> argh. 🙁
<leorize[m]> @kaushalmodi: that doesn't sound too bad, though adding yet another pragma might not be too appealing
Kaushal Modi
@kaushalmodi
leorize[m]: from my perspective, it looks like:
  • most of exportc's use requires dynlib too, so may be exportc should automatically behave as if dynlib was used
  • dynlib can then be deprecated
  • a new pragma.. .local.? would then export the symbols locally instead of globally
essentially default exportc to do global exports as before and introduce a new pragma to specify local exports
From IRC (bridge bot)
@FromIRC
<disruptek> what am i looking at?
<disruptek> a crappy c header?
<FromDiscord> <clyybber> a funny file name
<FromDiscord> <clyybber> at least when you are 10-yo
<disruptek> ah
<disruptek> gay is the author of another algo.
<disruptek> isn't he?
<FromDiscord> <clyybber> yeah, think so
<disruptek> you think he's gay?
Kaushal Modi
@kaushalmodi
leorize[m]: I need to sign off, but we can continue our discussion on https://github.com/nim-lang/Nim/issues/13416#issuecomment-586505903
From IRC (bridge bot)
@FromIRC
<disbot> ➥ 3[devel regression] {.exportc.} tagged procs no longer export to compiled .so objects ; snippet at https://play.nim-lang.org/#ix=2bJM
<FromDiscord> <clyybber> disruptek: Fo ssure
<FromDiscord> <clyybber> disruptek: Btw, I'm porting ryus table generation code to nim
From IRC (bridge bot)
@FromIRC
<FromDiscord> <clyybber> so we can generate the tables at compile time
<disruptek> this is the generic version, right?
<Araq> btw my concern for code size was serious
<FromDiscord> <clyybber> disruptek: Nope
<FromDiscord> <clyybber> Araq: Ok, I'm still doing this. Maybe I get it managable
<Araq> would be a shame to add 4kb for $myfloat
<FromDiscord> <clyybber> Yeah
<FromDiscord> <clyybber> I agree
<disruptek> that's why the one that goes in has to be the nim one.
<FromDiscord> <clyybber> hmm
<FromDiscord> <clyybber> maybe its best we port a non-microoptimized to hell algorithm