<zacts>can guile utilize Rust libraries? <zacts>or can guile be used as a Rust extension language? <ijp>I mean, maybe you could somehow do the latter, but I foresee a bunch of problems <zacts>that's fine. I wonder if guile can borrow into chicken scheme somehow at the C level <zacts>my reasoning behind these questions is I guess, I wonder if guile can utilize llvm, and if guile can utilize C FFI <ijp>assuming rust can utilise C which called guile <Chaos`Eternal>which means you can using guile ffi mechanism to use Rust lib <galex-713>wingo: civodul: any news about debugger ,break-at-source still not working? <galex-713>But I’d like to benefit of the guile debugger <wingo>galex-713: a test case would be appreciated :) <wingo>i don't use breakpoitns usually <galex-713>you just c-x c-e and make sequentially temporary variables to imitate local environnement? <wingo>i don't use geiser because my guile is usually broken :) <wingo>when there is an error i use ,locals <galex-713>wingo: and what when there’s no error and you just get unintended result? <wingo>i insert printouts into the code usually <galex-713>wingo: I mean, if I do ,bs cormen.scm 40 for example, repl print newline and wait undefinitely <wingo>sorry, i don't have time right now :/ <civodul>i don't know what you're talking about, could you explain" ***dsmith_ is now known as dsmith
<civodul>"Programming language Theme-D extends Scheme with static typing. Currently Theme-D is implemented as a <daviid>ACTION thinnks that these implementations should be called '... reduces Scheme to static typing ...', not '... extends ...' <ijp>ACTION whacks daviid upside the haid <civodul>it looks like there's no limit on the complexity of this language <wleslie>mental note: reference initialisation -> safe-search on <civodul>i happen to be paid for writing C++, among other things <civodul>i thought i'd use this fancy new C++11 rvalue references&& so i could look smart <profan>and his obituary would spell out "perished while trying to comprehend the c++ standard" <wleslie>didn't realise that reading more than 529 bytes of the spec at a time was undefined behaviour, and accidentally optimised himself out of existence <wleslie>it's both a reference to a reference, and an and <dsmith>Next thing you know they'll make shifts do I/O <civodul>dsmith: and and you thought it was a typo? <profan>any bets on if they'll ever introduce yet another reference type? <dsmith>I was reading that link, and then suddenly I remember && was and. <profan>i'm guessing it might become a possibility now that they're chasing lifetime stuff too <dsmith>And then the top of my head popped off <wleslie>they will probably want to support both footnotes and endnotes for the next standard <dsmith>With little bits of confetti flying around. <dsmith>So if you int&& rref = 1; and then rref = 2; Does that make all 1's 2's ?? ( not serious. Don't think you can assign to a reference?) <dsmith>I started learning c++ in 1985 or so. But I stopped and kept putting it off because they kept changing it. (the *next* version will have exceptions.. THe *next* version will have blahh) <dsmith>wingo, If you didn't see yet. I think your 32bit fix did it. But there are other problems. <galex-713>civodul: you know, the REPL ,break-at-source command <civodul>i know the command, yes, so what's the problem? :-) <civodul>in general it's best to send bug reports to bug-guile@gnu.org <rekado_>hey Guilers, does Guile have anything comparable to racket's contracts? <galex-713>if I do ,bs cormen.scm 40 I get ERROR: No procedures found at ~a:~a. "cormen.scm" 31 <rekado_>as someone exiled from the land of Haskell it's something I really miss in Scheme. <civodul>i didn't know you were "from the land of Haskell" :-) <galex-713>even with an absolute path it says “no procedure found” <galex-713>civodul: so why doesn’t it find a procedure? <galex-713>yeah someone said me that pre-last time I asked <galex-713>That why I asked you and wingo if it was fixed <civodul>it won't be fixed until a bug is reported, and that's where you come in! :-) <civodul>please send it to bug-guile@gnu.org so someone can process it as time permits <galex-713>civodul: is there a process/standard of bug-reporting about the info I should give that I should learn before? if so where is it described? <civodul>galex-713: unfortunately i don't think it is well describe, but in this case here, it's enough to (1) give the Guile version you're using, and (2) provide an example to reproduce it (e.g., transcript of a Guile session) <galex-713>How do you know the current directory where guile is running?