>From the output you showed, you seem to have only replaced the "rackunit"
package, which is just a stub to depend on the "rackunit-lib",
"rackunit-doc", "rackunit-gui," and "rackunit-plugin-lib", packages—those
you still have installed in the installation default place. It also looks
like you
Here are some notes that I wrote to deal with this situation, except they
use the plot package:
https://alex-hhh.github.io/2018/01/changing-built-in-racket-packages.html
You will also find some more information about this topic if you search
this group, but most of what is explained in
If I'm reading docs right, then it should've worked, hm:
Conflict checking disallows installation of the same or conflicting package
> in different scopes, but if such a configuration is forced, collections are
> found first in packages with user package scope
>
I thought about hacking on /rackunit/ a bit and if it pans out maybe send
my changes upstream. Typically I would clone a repo and then do raco pkg
install in its folder so that I have it linked and code that may require it
picks up latest changes. Very convenient workflow. Except /rackunit/ is
DEADLINE: 15 May 2019, (Any time in the world)
WEBSITE: https://icfp19.sigplan.org/home/minikanren-2019
LOCATION: Berlin, Germany (co-located with ICFP)
DATE: 22 August 2019
The 2019 First miniKanren and Relational Programming Workshop is calling
for submissions.
Full papers are due 15 May
Hi Greg,
Thank you for the very detailed explanation. I was also very much not
my intention to belittle racket-mode and I will evoke my "yes indeed my
knowledge was quite incomplete." I have learned many very useful things
from this thread (C-u C-c C-c is a reminder that stopping by the manual
> On Apr 5, 2019, at 3:23 AM, zeRusski wrote:
>
> Now about that error in the docs:
I was skeptical, but I think you're right:
"More generally, we can define binding based on subsets: A reference’s binding
is found as one whose set of scopes is a subset of the reference’s own scopes
(in
A simple model to keep in your head:
> Each macro keeps a count, i, of how many times it has been applied.
> Each time a the output of a macro contains a definition of name not
> present in the input it appends _i to the name.
>
Ha, I get it. That's a good little heuristic. I'm keeping
Yes!
fre. 5. apr. 2019 kl. 13.52 skrev Hendrik Boom :
> On Fri, Apr 05, 2019 at 01:35:37PM +0200, Jens Axel Søgaard wrote:
> > Den tor. 4. apr. 2019 kl. 21.58 skrev zeRusski >:
> >
> > (define-simple-macro (define-foo (name:id formal:id ...) body:expr ...)
> > >> (begin
> > >> (define
On Fri, Apr 05, 2019 at 01:35:37PM +0200, Jens Axel Søgaard wrote:
> Den tor. 4. apr. 2019 kl. 21.58 skrev zeRusski :
>
> (define-simple-macro (define-foo (name:id formal:id ...) body:expr ...)
> >> (begin
> >> (define (foo-impl formal ...) body ...)
> >> (define-syntax (name stx)
> >>
Den tor. 4. apr. 2019 kl. 21.58 skrev zeRusski :
(define-simple-macro (define-foo (name:id formal:id ...) body:expr ...)
>> (begin
>> (define (foo-impl formal ...) body ...)
>> (define-syntax (name stx)
>> (syntax-parse stx
>> [(_ . args) #'(foo-impl . args)]
>>
> If I understand correctly, the fourth paragraph here is relevant?
>
>
> https://docs.racket-lang.org/reference/syntax-model.html#%28part._transformer-model%29
>
>
>
I dreaded someone pointing me there. I read it a year ago, took a lot of
head scratching and careful reading before I
12 matches
Mail list logo
