Re: [racket-users] Embedded racket (cs) question

2020-07-14 Thread Nate Griswold
Great, thanks for all of that digging. Ya, i think i will go the non-declare_modules, non-ctool route for now as i think this fits my use-case pretty well. I want to allow access to the full racket library for racket code that changes often. Nate On Mon, Jul 13, 2020 at 8:32 PM Matthew Flatt

Re: [racket-users] Embedded racket (cs) question

2020-07-13 Thread Matthew Flatt
Thanks for the example! I did not guess correctly about your mixture of embedded modules and `dynamic-require`. The short answer is that you should either embed modules or reference them through an external paths like "/Applications/Racket v7.7/collects", but not both. Otherwise, the two worlds

Re: [racket-users] Embedded racket (cs) question

2020-07-13 Thread Nate Griswold
I put up a repo with the bug at https://github.com/nwg/racket-expo The stack trace is this: build-path: contract violation expected: (or/c path-string? path-for-some-system? 'up 'same) given: # context...: do-raise-argument-error loop build proc

Re: [racket-users] Embedded racket (cs) question

2020-07-13 Thread Ryan Culpepper
I don't know if it helps, but config:installation-name is a promise defined by setup/private/dirs. Ryan On Mon, Jul 13, 2020 at 7:23 PM Matthew Flatt wrote: > I'm not sure how it could be in `dynamic-require` itself, as opposed to > a library that is loaded by `dynamic-require`, but it sounds

Re: [racket-users] Embedded racket (cs) question

2020-07-13 Thread Matthew Flatt
I'm not sure how it could be in `dynamic-require` itself, as opposed to a library that is loaded by `dynamic-require`, but it sounds like a bug at some level. Can you provide a small example? At Mon, 13 Jul 2020 11:03:41 -0500, Nate Griswold wrote: > Sam, thanks > > To be clear, this crash

Re: [racket-users] Embedded racket (cs) question

2020-07-13 Thread Nate Griswold
Sam, thanks To be clear, this crash happened DURING a dynamic-require and judging by the stack trace looked to be part of the dynamic-require machinery (and this seems to depend on the installation name). I actually wasn't depending on anything but racket/base, so i don't believe anything i was

Re: [racket-users] Embedded racket (cs) question

2020-07-13 Thread Sam Tobin-Hochstadt
My guess, not having looked further than your email, is that when you don't include racket/promise, something is supplying a promise to something else but there are two different instantiations of the promise library, causing the force call from one not to recognize the promise from the other.

[racket-users] Embedded racket (cs) question

2020-07-13 Thread Nate Griswold
Hello. I noticed something and was wondering what the list thinks: I am using an embedded racket Ics) and i noticed that if i embed a file and don't include any libraries (for a very bare bones c file) i have problems with a crash on a promise on any dynamic-require: build-path: contract