Hi Racketeers,
I’m creating a macro that collects values in the internal-definition
context. E.g.,
($list
1
(define x 2)
x)
should evaluate to '(1 2).
Here’s my implementation, and it kinda works:
#lang racket
(begin-for-syntax
(define ((do-it gs ctx) e)
(let loop ([e e])
(defi
I'm pleased to report that the "rename swap" of Originalname ->
Originalname-x -> originalname worked like a charm :) It also preserved the
metadata. Also, the dependent packages built successfully within about an
hour of the upstream rename. Thank you both for your suggestions and input.
If anyon
In October 2020, we'll be holding a virtual RacketCon, rather than an
in-person meeting as usual. We hope to get back to normal in 2021. We
have not worked out the exact dates and details, but have a few
parameters.
We're thinking about following PLDI, where the general model is to
have pre-record
Got it. I'll change that, and thank you.
On Fri, Jun 5, 2020 at 11:28 AM Sam Tobin-Hochstadt
wrote:
> This most likely means that your documentation is in a file with a generic
> name like manual.scrbl which those packages also use.
>
> Sam
>
> On Fri, Jun 5, 2020, 11:20 AM David Storrs wrote:
I'm looking at profiling some code for performance and tried out the Racket
profile package but I'm not sure what the numbers mean.
Here is a very simple example:
https://stackoverflow.com/questions/23988370/thorough-guide-for-profiling-racket-code
Here's a run from my actual code:
https://git
This most likely means that your documentation is in a file with a generic
name like manual.scrbl which those packages also use.
Sam
On Fri, Jun 5, 2020, 11:20 AM David Storrs wrote:
> I uploaded a new module, 'thread-with-id', and the package server tells me
> that there are conflicts. The me
I uploaded a new module, 'thread-with-id', and the package server tells me
that there are conflicts. The message is:
https://pkg-build.racket-lang.org/conflicts.txt
doc "main":
ekans lti-freq-domain-toolbox protobuf thread-with-id
I'm not sure what this means -- I've looked through the ekans
I think the package name system is case-insensitive (??) but
case-preserving (definitely), and certainly objects to trying to create two
packages that differ only in case.
So renaming from FOO to foo won't work, because it considers this an
attempt to overwrite an existing package. I think. We
8 matches
Mail list logo