This is helpful! Thank you. Gives me a few more options to try, though I
still don't have a perfect solution.
Regarding intent, yes, I want to have a development environment based on a
git clone, with a package behavior that mimics identically the experience
seen by someone who downloaded my
I am having problems installing raco docs, meaning I want
raco docs foo-pkg
to work no matter how I installed the package. To give you an example of a
failure, I created a racket package and put it up on the raco pkg server:
https://pkgd.racket-lang.org/pkgn/package/bleir-sandbox
ogous facilities in racket, like the
> kind Brian asked about, I'd love to know as well.
>
>
> On Fri, Oct 29, 2021 at 3:14 PM Brian Beckman wrote:
>
>> Well, as I understand it, a struct (usually? always?), #:transparent or
>> not, when declared, defines symbols that a
I believe that run time will be the most plausible use case. I may write
macros that refer to struct-procedure names at macro-writing time, but I
don't expect to invoke the struct procedures at macro-expansion time. My
primary issue is "discoverability:" how can I find out the interface of any
>>>
>>>>> ;;
>>>>> https://stackoverflow.com/questions/20076868/how-to-know-whether-a-racket-variable-is-defined-or-not
>>>>> (define-syntax (defined? stx)
>>>>> (syntax-case stx ()
>>>>> [(_ id)
&
sym)
> (let ([names (map (λ (s)
> (string->symbol
> (format "~a-~a" (syntax-e #'sym) s)))
>(struct-field-info-list
> (syntax-local-value #'sym))
>)])
> #`(a
re going on under the hood.
>
> I would say that studying the code for *struct-plus-plus* could also be
> informative, as it would provide a way to see how a struct system that
> provides the kind of visibility you were looking for achieves that
> visibility, and how it inter
foo-a, foo-b,
plus anything else the author of foo (the type) wants me to see.
On Fri, Oct 29, 2021 at 1:45 PM John Clements
wrote:
> In the text below, you refer to the “public” interface. Can I ask what you
> mean by “public” in this context?
>
> John
>
> > On Oct 29,
8 matches
Mail list logo