[racket-users] How do I represent a convenient two-step allocation using ffi/unsafe?

Consider the following C++ that calls a function once to learn how much it should allocate for a vector, and again to populate said vector. uint32_t count; vkEnumerateInstanceLayerProperties(, NULL); std::vector properties(count); vkEnumerateInstanceLayerProperties(, properties.data());

Re: [racket-users] Scribble examples performance

I think the evaluators are being closed, because I'm using make-base-eval-factory and the #:close option. Do evaluator *factories* need to be closed? On Sat, Oct 19, 2019, 8:05 AM Sam Tobin-Hochstadt wrote: > One thing that's important that we've found improves performance is to > close the

Re: [racket-users] Vulkan integration ready for first round of testing

Thanks for doing this. This might be of interest to for potential racket game jam participants.! S. On Fri, Oct 18, 2019 at 7:26 PM Sage Gerard wrote: > I think I'm ready to do my first rounds writing/supporting Vulkan > applications. It would not surprise me if some design gaps pop up, but I

Re: [racket-users] Scribble examples performance

One thing that's important that we've found improves performance is to close the evaluator at the end of the module. Sam On Sat, Oct 19, 2019, 3:43 AM Jack Firth wrote: > The Scribble docs for my Rebellion > package take nearly two minutes > to build. I

[racket-users] Scribble examples performance

The Scribble docs for my Rebellion package take nearly two minutes to build. I have a hunch that most of the time is spent compiling, evaluating, and rendering example code. Every one of my Scribble modules is structured roughly like this: #lang