Re: [racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread David Storrs
On Tue, Oct 13, 2020 at 6:52 PM William J. Bowman 
wrote:

> > >>> @defproc[(trie-add-item+data! [arg trie?][item (listof
> any/c)][#:combine
> Is the issue that you rebound `item`?
>
>
...

Yes.  Yes, that is exactly the issue.  I hate my life.

Thank you.


On Tue, Oct 13, 2020 at 10:20:24AM -0700, Sorawee Porncharoenwase wrote:
> > apparently it doesn’t like having an itemlist inside of a {} block at all
> >
> > I’m not sure if I totally understand it, but this doesn’t appear to be
> > true. The below doc renders correctly as I expect.
> >
> > #lang scribble/manual
> >
> > @itemlist[
> >   @item{foo
> > @itemlist[
> >   @item{bar}
> >   @item{baz}]
> > hello
> > @itemlist[
> >   @item{world}]}
> >  @item{foo2
> > @itemlist[
> >   @item{bar2}
> >   @item{baz2}]
> > hello2
> > @itemlist[
> >   @item{world2}]}]
> >
> >
> > On Tue, Oct 13, 2020 at 10:09 AM David Storrs 
> > wrote:
> >
> > > Okay, apparently it doesn't like having an itemlist inside of a {}
> block
> > > at all, but as long as it's outside of one then nested lists are fine.
> > > Ugh.  I know Scribble is super good because it makes beautiful
> > > documentation and does cross-linking and examples and all that, but
> it's
> > > also a complete pain in the ass unless you're expert with it.
> > >
> > > Sorry for wasting everyone's time.
> > >
> > > On Tue, Oct 13, 2020 at 1:02 PM David Storrs 
> > > wrote:
> > >
> > >> Argh.  Wrong code.  Please ignore prior message.
> > >>
> > >> On Tue, Oct 13, 2020 at 12:57 PM David Storrs  >
> > >> wrote:
> > >>
> > >>>
> > >>>
> > >>> On Tue, Oct 13, 2020 at 12:48 PM Ben Greenman <
> > >>> benjaminlgreen...@gmail.com> wrote:
> > >>>
> >  On 10/13/20, David Storrs  wrote:
> >  > @itemlist[
> >  >   @item{The size cage needed depends on the type of dog
> >  >   @itemlist[
> >  > @item{Pug:  Small}
> >  > @item{Collie: Medium}
> >  > @item{Mastiff:  Large}]}]
> >  >
> >  > I would like to produce something that looks like this:
> >  >
> >  >- The size cage needed depends on the type of dog
> >  >   - Pug: Small
> >  >   - Collie: Medium
> >  >   - Mastiff: Large
> >  >
> >  > Is there a correct way to do this?
> > 
> >  What you have looks good to me in #lang scribble/manual
> > 
> > 
> > >>> Here's the actual code:
> > >>>
> > >>> @defproc[(trie-add-item+data! [arg trie?][item (listof
> any/c)][#:combine
> > >>> combine-method (or/c 'keep 'replace 'meld/current 'meld/new (->
> trie-node?
> > >>> trie-node? trie-node?)) 'meld/new]) trie?]{Adds one item to the trie
> where
> > >>> the elements of the list are considered to be elements of the item.
> If an
> > >>> item is a @racket[cons] pair where the @racket[cdr] is a
> > >>> @racket[trie-node?] then the @racket[car] will be used as the
> element and
> > >>> the @racket[cdr] will be the data attached to that node.  The final
> node is
> > >>> marked as terminal regardless of whether it already existed.
> > >>>
> > >>> If an element of the item already exists in the trie then that
> element
> > >>> will be updated based on the combine method specified via the
> > >>> @racket[#:combine] keyword.  Specifically:
> > >>>
> > >>> @itemlist[
> > >>> @item{test}
> > >>> ]
> > >>> }
> > >>>
> > >>> Here's the error output:
> > >>>
> > >>> trie.scrbl:165:0: item: misuse of an identifier (not in `racket',
> etc.)
> > >>> that is bound as a code-typesetting variable
> > >>>   in: (item "test")
> > >>>   location...:
> > >>>trie.scrbl:165:0
> > >>>   context...:
> > >>>do-raise-syntax-error
> > >>>apply-transformer-in-context
> > >>>apply-transformer
> > >>>dispatch-transformer
> > >>>for-loop
> > >>>[repeats 2 more times]
> > >>>finish-bodys
> > >>>lambda-clause-expander
> > >>>for-loop
> > >>>[repeats 1 more time]
> > >>>finish-bodys
> > >>>for-loop
> > >>>finish-bodys
> > >>>loop
> > >>>for-loop
> > >>>[repeats 3 more times]
> > >>>
> > >>>
> > >>> It works fine if I remove the inner @itemlist.  What should I do
> > >>> differently?
> > >>>
> > >>> --
> >  You received this message because you are subscribed to the Google
> >  Groups "Racket Users" group.
> >  To unsubscribe from this group and stop receiving emails from it,
> send
> >  an email to racket-users+unsubscr...@googlegroups.com.
> >  To view this discussion on the web visit
> > 
> https://groups.google.com/d/msgid/racket-users/CAFUu9R4-4BO3Gi2PDxZ%3D2BbQCrJP4O%2BkAWT1f7DJJtFapFdYTA%40mail.gmail.com
> >  .
> > 
> > >>> --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Racket Users" group.
> > > To unsubscribe from this group and stop receiving emails from it, send
> an
> > > email to racket-users+unsubscr...@googlegroups.com.
> > > To view this discussion on the web 

Re: [racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread William J. Bowman
> >>> @defproc[(trie-add-item+data! [arg trie?][item (listof any/c)][#:combine
Is the issue that you rebound `item`?

On Tue, Oct 13, 2020 at 10:20:24AM -0700, Sorawee Porncharoenwase wrote:
> apparently it doesn’t like having an itemlist inside of a {} block at all
> 
> I’m not sure if I totally understand it, but this doesn’t appear to be
> true. The below doc renders correctly as I expect.
> 
> #lang scribble/manual
> 
> @itemlist[
>   @item{foo
> @itemlist[
>   @item{bar}
>   @item{baz}]
> hello
> @itemlist[
>   @item{world}]}
>  @item{foo2
> @itemlist[
>   @item{bar2}
>   @item{baz2}]
> hello2
> @itemlist[
>   @item{world2}]}]
> 
> 
> On Tue, Oct 13, 2020 at 10:09 AM David Storrs 
> wrote:
> 
> > Okay, apparently it doesn't like having an itemlist inside of a {} block
> > at all, but as long as it's outside of one then nested lists are fine.
> > Ugh.  I know Scribble is super good because it makes beautiful
> > documentation and does cross-linking and examples and all that, but it's
> > also a complete pain in the ass unless you're expert with it.
> >
> > Sorry for wasting everyone's time.
> >
> > On Tue, Oct 13, 2020 at 1:02 PM David Storrs 
> > wrote:
> >
> >> Argh.  Wrong code.  Please ignore prior message.
> >>
> >> On Tue, Oct 13, 2020 at 12:57 PM David Storrs 
> >> wrote:
> >>
> >>>
> >>>
> >>> On Tue, Oct 13, 2020 at 12:48 PM Ben Greenman <
> >>> benjaminlgreen...@gmail.com> wrote:
> >>>
>  On 10/13/20, David Storrs  wrote:
>  > @itemlist[
>  >   @item{The size cage needed depends on the type of dog
>  >   @itemlist[
>  > @item{Pug:  Small}
>  > @item{Collie: Medium}
>  > @item{Mastiff:  Large}]}]
>  >
>  > I would like to produce something that looks like this:
>  >
>  >- The size cage needed depends on the type of dog
>  >   - Pug: Small
>  >   - Collie: Medium
>  >   - Mastiff: Large
>  >
>  > Is there a correct way to do this?
> 
>  What you have looks good to me in #lang scribble/manual
> 
> 
> >>> Here's the actual code:
> >>>
> >>> @defproc[(trie-add-item+data! [arg trie?][item (listof any/c)][#:combine
> >>> combine-method (or/c 'keep 'replace 'meld/current 'meld/new (-> trie-node?
> >>> trie-node? trie-node?)) 'meld/new]) trie?]{Adds one item to the trie where
> >>> the elements of the list are considered to be elements of the item.  If an
> >>> item is a @racket[cons] pair where the @racket[cdr] is a
> >>> @racket[trie-node?] then the @racket[car] will be used as the element and
> >>> the @racket[cdr] will be the data attached to that node.  The final node 
> >>> is
> >>> marked as terminal regardless of whether it already existed.
> >>>
> >>> If an element of the item already exists in the trie then that element
> >>> will be updated based on the combine method specified via the
> >>> @racket[#:combine] keyword.  Specifically:
> >>>
> >>> @itemlist[
> >>> @item{test}
> >>> ]
> >>> }
> >>>
> >>> Here's the error output:
> >>>
> >>> trie.scrbl:165:0: item: misuse of an identifier (not in `racket', etc.)
> >>> that is bound as a code-typesetting variable
> >>>   in: (item "test")
> >>>   location...:
> >>>trie.scrbl:165:0
> >>>   context...:
> >>>do-raise-syntax-error
> >>>apply-transformer-in-context
> >>>apply-transformer
> >>>dispatch-transformer
> >>>for-loop
> >>>[repeats 2 more times]
> >>>finish-bodys
> >>>lambda-clause-expander
> >>>for-loop
> >>>[repeats 1 more time]
> >>>finish-bodys
> >>>for-loop
> >>>finish-bodys
> >>>loop
> >>>for-loop
> >>>[repeats 3 more times]
> >>>
> >>>
> >>> It works fine if I remove the inner @itemlist.  What should I do
> >>> differently?
> >>>
> >>> --
>  You received this message because you are subscribed to the Google
>  Groups "Racket Users" group.
>  To unsubscribe from this group and stop receiving emails from it, send
>  an email to racket-users+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit
>  https://groups.google.com/d/msgid/racket-users/CAFUu9R4-4BO3Gi2PDxZ%3D2BbQCrJP4O%2BkAWT1f7DJJtFapFdYTA%40mail.gmail.com
>  .
> 
> >>> --
> > You received this message because you are subscribed to the Google Groups
> > "Racket Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to racket-users+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/racket-users/CAE8gKocp9RQ0cV1OL1dAAH%2B4CevDVTfHvd8Xf5o%3DP5KGeUZwjg%40mail.gmail.com
> > 
> > .
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe 

[racket-users] Racket-mode (emacs) get coverage without using test submodule

2020-10-13 Thread 'Julian' via Racket Users
 Hi,

For reasons X and Y that I won't get into I'm using Emacs instead of 
DrRacket for writing racket code for the Programming languages class that 
I'm taking. I have found that racket-mode (as recommended by 
https://docs.racket-lang.org/guide/Emacs.html) is able to do a lot of neat 
things and most of what I need to code. 

The one limitation that I have run into is running my code and getting any 
kind of coverage information, whether that's visual highlighting or a 
printout in the REPL. At the moment I use DrRacket exclusively for this 
task. Back in the racket-mode Emacs world the closest thing that I have 
found is this: 
https://racket-mode.com/#racket_002dtest

However, this method not flexible enough since it requires me to put my 
tests in the following form, which differs from the test writing convention 
that I have to follow for this class:
(module+ test (require rackunit) (check-true #t))

I have heard that xrepl should be able to help me since I should be able to 
use
,coverage
but when I try to require it in the repl I get the following:

hw4.rkt> (require xrepl)
; hw4.rkt::424: Type Checker: missing type for top-level identifier;
;  either undefined or missing a type annotation
;   identifier: require
;   in: require
; Context:
;  /usr/racket/collects/syntax/private/id-table.rkt:454:11 free-id-table-ref
;  /usr/racket/collects/syntax/private/id-table.rkt:454:11 free-id-table-ref

The racket language I'm using is a custom teaching language (#lang pl 04) 
available here .

Does anyone have any ideas on how I could get coverage to work directly 
with racket-mode or with xrepl still inside of Emacs?

Background: I'm not experienced with Racket (only have knowledge of [B/I]SL 
languages and what I'm learning in this class) and I'm also not an Emacs 
wizard.

Thanks for the help.
- Julian

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/63680eec-824b-4460-a6f2-d225374b8597n%40googlegroups.com.


Re: [racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread Sorawee Porncharoenwase
apparently it doesn’t like having an itemlist inside of a {} block at all

I’m not sure if I totally understand it, but this doesn’t appear to be
true. The below doc renders correctly as I expect.

#lang scribble/manual

@itemlist[
  @item{foo
@itemlist[
  @item{bar}
  @item{baz}]
hello
@itemlist[
  @item{world}]}
 @item{foo2
@itemlist[
  @item{bar2}
  @item{baz2}]
hello2
@itemlist[
  @item{world2}]}]


On Tue, Oct 13, 2020 at 10:09 AM David Storrs 
wrote:

> Okay, apparently it doesn't like having an itemlist inside of a {} block
> at all, but as long as it's outside of one then nested lists are fine.
> Ugh.  I know Scribble is super good because it makes beautiful
> documentation and does cross-linking and examples and all that, but it's
> also a complete pain in the ass unless you're expert with it.
>
> Sorry for wasting everyone's time.
>
> On Tue, Oct 13, 2020 at 1:02 PM David Storrs 
> wrote:
>
>> Argh.  Wrong code.  Please ignore prior message.
>>
>> On Tue, Oct 13, 2020 at 12:57 PM David Storrs 
>> wrote:
>>
>>>
>>>
>>> On Tue, Oct 13, 2020 at 12:48 PM Ben Greenman <
>>> benjaminlgreen...@gmail.com> wrote:
>>>
 On 10/13/20, David Storrs  wrote:
 > @itemlist[
 >   @item{The size cage needed depends on the type of dog
 >   @itemlist[
 > @item{Pug:  Small}
 > @item{Collie: Medium}
 > @item{Mastiff:  Large}]}]
 >
 > I would like to produce something that looks like this:
 >
 >- The size cage needed depends on the type of dog
 >   - Pug: Small
 >   - Collie: Medium
 >   - Mastiff: Large
 >
 > Is there a correct way to do this?

 What you have looks good to me in #lang scribble/manual


>>> Here's the actual code:
>>>
>>> @defproc[(trie-add-item+data! [arg trie?][item (listof any/c)][#:combine
>>> combine-method (or/c 'keep 'replace 'meld/current 'meld/new (-> trie-node?
>>> trie-node? trie-node?)) 'meld/new]) trie?]{Adds one item to the trie where
>>> the elements of the list are considered to be elements of the item.  If an
>>> item is a @racket[cons] pair where the @racket[cdr] is a
>>> @racket[trie-node?] then the @racket[car] will be used as the element and
>>> the @racket[cdr] will be the data attached to that node.  The final node is
>>> marked as terminal regardless of whether it already existed.
>>>
>>> If an element of the item already exists in the trie then that element
>>> will be updated based on the combine method specified via the
>>> @racket[#:combine] keyword.  Specifically:
>>>
>>> @itemlist[
>>> @item{test}
>>> ]
>>> }
>>>
>>> Here's the error output:
>>>
>>> trie.scrbl:165:0: item: misuse of an identifier (not in `racket', etc.)
>>> that is bound as a code-typesetting variable
>>>   in: (item "test")
>>>   location...:
>>>trie.scrbl:165:0
>>>   context...:
>>>do-raise-syntax-error
>>>apply-transformer-in-context
>>>apply-transformer
>>>dispatch-transformer
>>>for-loop
>>>[repeats 2 more times]
>>>finish-bodys
>>>lambda-clause-expander
>>>for-loop
>>>[repeats 1 more time]
>>>finish-bodys
>>>for-loop
>>>finish-bodys
>>>loop
>>>for-loop
>>>[repeats 3 more times]
>>>
>>>
>>> It works fine if I remove the inner @itemlist.  What should I do
>>> differently?
>>>
>>> --
 You received this message because you are subscribed to the Google
 Groups "Racket Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to racket-users+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/racket-users/CAFUu9R4-4BO3Gi2PDxZ%3D2BbQCrJP4O%2BkAWT1f7DJJtFapFdYTA%40mail.gmail.com
 .

>>> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-users/CAE8gKocp9RQ0cV1OL1dAAH%2B4CevDVTfHvd8Xf5o%3DP5KGeUZwjg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CADcuegs-94OYHQi9JMx%2BsdqQdA2RM_Fg2sCLRxYQdLycJsvjcQ%40mail.gmail.com.


Re: [racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread David Storrs
Okay, apparently it doesn't like having an itemlist inside of a {} block at
all, but as long as it's outside of one then nested lists are fine.  Ugh.
I know Scribble is super good because it makes beautiful documentation and
does cross-linking and examples and all that, but it's also a complete pain
in the ass unless you're expert with it.

Sorry for wasting everyone's time.

On Tue, Oct 13, 2020 at 1:02 PM David Storrs  wrote:

> Argh.  Wrong code.  Please ignore prior message.
>
> On Tue, Oct 13, 2020 at 12:57 PM David Storrs 
> wrote:
>
>>
>>
>> On Tue, Oct 13, 2020 at 12:48 PM Ben Greenman <
>> benjaminlgreen...@gmail.com> wrote:
>>
>>> On 10/13/20, David Storrs  wrote:
>>> > @itemlist[
>>> >   @item{The size cage needed depends on the type of dog
>>> >   @itemlist[
>>> > @item{Pug:  Small}
>>> > @item{Collie: Medium}
>>> > @item{Mastiff:  Large}]}]
>>> >
>>> > I would like to produce something that looks like this:
>>> >
>>> >- The size cage needed depends on the type of dog
>>> >   - Pug: Small
>>> >   - Collie: Medium
>>> >   - Mastiff: Large
>>> >
>>> > Is there a correct way to do this?
>>>
>>> What you have looks good to me in #lang scribble/manual
>>>
>>>
>> Here's the actual code:
>>
>> @defproc[(trie-add-item+data! [arg trie?][item (listof any/c)][#:combine
>> combine-method (or/c 'keep 'replace 'meld/current 'meld/new (-> trie-node?
>> trie-node? trie-node?)) 'meld/new]) trie?]{Adds one item to the trie where
>> the elements of the list are considered to be elements of the item.  If an
>> item is a @racket[cons] pair where the @racket[cdr] is a
>> @racket[trie-node?] then the @racket[car] will be used as the element and
>> the @racket[cdr] will be the data attached to that node.  The final node is
>> marked as terminal regardless of whether it already existed.
>>
>> If an element of the item already exists in the trie then that element
>> will be updated based on the combine method specified via the
>> @racket[#:combine] keyword.  Specifically:
>>
>> @itemlist[
>> @item{test}
>> ]
>> }
>>
>> Here's the error output:
>>
>> trie.scrbl:165:0: item: misuse of an identifier (not in `racket', etc.)
>> that is bound as a code-typesetting variable
>>   in: (item "test")
>>   location...:
>>trie.scrbl:165:0
>>   context...:
>>do-raise-syntax-error
>>apply-transformer-in-context
>>apply-transformer
>>dispatch-transformer
>>for-loop
>>[repeats 2 more times]
>>finish-bodys
>>lambda-clause-expander
>>for-loop
>>[repeats 1 more time]
>>finish-bodys
>>for-loop
>>finish-bodys
>>loop
>>for-loop
>>[repeats 3 more times]
>>
>>
>> It works fine if I remove the inner @itemlist.  What should I do
>> differently?
>>
>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Racket Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to racket-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/racket-users/CAFUu9R4-4BO3Gi2PDxZ%3D2BbQCrJP4O%2BkAWT1f7DJJtFapFdYTA%40mail.gmail.com
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAE8gKocp9RQ0cV1OL1dAAH%2B4CevDVTfHvd8Xf5o%3DP5KGeUZwjg%40mail.gmail.com.


Re: [racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread David Storrs
Argh.  Wrong code.  Please ignore prior message.

On Tue, Oct 13, 2020 at 12:57 PM David Storrs 
wrote:

>
>
> On Tue, Oct 13, 2020 at 12:48 PM Ben Greenman 
> wrote:
>
>> On 10/13/20, David Storrs  wrote:
>> > @itemlist[
>> >   @item{The size cage needed depends on the type of dog
>> >   @itemlist[
>> > @item{Pug:  Small}
>> > @item{Collie: Medium}
>> > @item{Mastiff:  Large}]}]
>> >
>> > I would like to produce something that looks like this:
>> >
>> >- The size cage needed depends on the type of dog
>> >   - Pug: Small
>> >   - Collie: Medium
>> >   - Mastiff: Large
>> >
>> > Is there a correct way to do this?
>>
>> What you have looks good to me in #lang scribble/manual
>>
>>
> Here's the actual code:
>
> @defproc[(trie-add-item+data! [arg trie?][item (listof any/c)][#:combine
> combine-method (or/c 'keep 'replace 'meld/current 'meld/new (-> trie-node?
> trie-node? trie-node?)) 'meld/new]) trie?]{Adds one item to the trie where
> the elements of the list are considered to be elements of the item.  If an
> item is a @racket[cons] pair where the @racket[cdr] is a
> @racket[trie-node?] then the @racket[car] will be used as the element and
> the @racket[cdr] will be the data attached to that node.  The final node is
> marked as terminal regardless of whether it already existed.
>
> If an element of the item already exists in the trie then that element
> will be updated based on the combine method specified via the
> @racket[#:combine] keyword.  Specifically:
>
> @itemlist[
> @item{test}
> ]
> }
>
> Here's the error output:
>
> trie.scrbl:165:0: item: misuse of an identifier (not in `racket', etc.)
> that is bound as a code-typesetting variable
>   in: (item "test")
>   location...:
>trie.scrbl:165:0
>   context...:
>do-raise-syntax-error
>apply-transformer-in-context
>apply-transformer
>dispatch-transformer
>for-loop
>[repeats 2 more times]
>finish-bodys
>lambda-clause-expander
>for-loop
>[repeats 1 more time]
>finish-bodys
>for-loop
>finish-bodys
>loop
>for-loop
>[repeats 3 more times]
>
>
> It works fine if I remove the inner @itemlist.  What should I do
> differently?
>
> --
>> You received this message because you are subscribed to the Google Groups
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to racket-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/racket-users/CAFUu9R4-4BO3Gi2PDxZ%3D2BbQCrJP4O%2BkAWT1f7DJJtFapFdYTA%40mail.gmail.com
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAE8gKoeGQ3BA-qUbNhWJebPV4%2BaLf7_9xJkcFFvRK-dDx%3Duj0w%40mail.gmail.com.


Re: [racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread David Storrs
On Tue, Oct 13, 2020 at 12:48 PM Ben Greenman 
wrote:

> On 10/13/20, David Storrs  wrote:
> > @itemlist[
> >   @item{The size cage needed depends on the type of dog
> >   @itemlist[
> > @item{Pug:  Small}
> > @item{Collie: Medium}
> > @item{Mastiff:  Large}]}]
> >
> > I would like to produce something that looks like this:
> >
> >- The size cage needed depends on the type of dog
> >   - Pug: Small
> >   - Collie: Medium
> >   - Mastiff: Large
> >
> > Is there a correct way to do this?
>
> What you have looks good to me in #lang scribble/manual
>
>
Here's the actual code:

@defproc[(trie-add-item+data! [arg trie?][item (listof any/c)][#:combine
combine-method (or/c 'keep 'replace 'meld/current 'meld/new (-> trie-node?
trie-node? trie-node?)) 'meld/new]) trie?]{Adds one item to the trie where
the elements of the list are considered to be elements of the item.  If an
item is a @racket[cons] pair where the @racket[cdr] is a
@racket[trie-node?] then the @racket[car] will be used as the element and
the @racket[cdr] will be the data attached to that node.  The final node is
marked as terminal regardless of whether it already existed.

If an element of the item already exists in the trie then that element will
be updated based on the combine method specified via the @racket[#:combine]
keyword.  Specifically:

@itemlist[
@item{test}
]
}

Here's the error output:

trie.scrbl:165:0: item: misuse of an identifier (not in `racket', etc.)
that is bound as a code-typesetting variable
  in: (item "test")
  location...:
   trie.scrbl:165:0
  context...:
   do-raise-syntax-error
   apply-transformer-in-context
   apply-transformer
   dispatch-transformer
   for-loop
   [repeats 2 more times]
   finish-bodys
   lambda-clause-expander
   for-loop
   [repeats 1 more time]
   finish-bodys
   for-loop
   finish-bodys
   loop
   for-loop
   [repeats 3 more times]


It works fine if I remove the inner @itemlist.  What should I do
differently?

-- 
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-users/CAFUu9R4-4BO3Gi2PDxZ%3D2BbQCrJP4O%2BkAWT1f7DJJtFapFdYTA%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAE8gKodk0yE3rNQwakRxTyvQYC9pXQmKfzwNUM1qR2dgjB75MA%40mail.gmail.com.


Re: [racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread Ben Greenman
On 10/13/20, David Storrs  wrote:
> @itemlist[
>   @item{The size cage needed depends on the type of dog
>   @itemlist[
> @item{Pug:  Small}
> @item{Collie: Medium}
> @item{Mastiff:  Large}]}]
>
> I would like to produce something that looks like this:
>
>- The size cage needed depends on the type of dog
>   - Pug: Small
>   - Collie: Medium
>   - Mastiff: Large
>
> Is there a correct way to do this?

What you have looks good to me in #lang scribble/manual

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAFUu9R4-4BO3Gi2PDxZ%3D2BbQCrJP4O%2BkAWT1f7DJJtFapFdYTA%40mail.gmail.com.


[racket-users] [scribble] Are nested lists possible?

2020-10-13 Thread David Storrs
@itemlist[
  @item{The size cage needed depends on the type of dog
  @itemlist[
@item{Pug:  Small}
@item{Collie: Medium}
@item{Mastiff:  Large}]}]

I would like to produce something that looks like this:

   - The size cage needed depends on the type of dog
  - Pug: Small
  - Collie: Medium
  - Mastiff: Large

Is there a correct way to do this?

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAE8gKoewMoNZKdsycdFuJmOvvdtfZi%3Do0hcfK%3Dmo9DFiDkoyQg%40mail.gmail.com.


[racket-users] Compiler Construction (CC) 2021 - Call for Papers

2020-10-13 Thread delphine...@gmail.com
ACM SIGPLAN 2021 International Conference on Compiler Construction (CC 2021)
Co-located with CGO, HPCA and PPoPP
Sat 27 February - Wed 3 March 2021
https://conf.researchr.org/home/CC-2021

CALL FOR PAPERS

The International Conference on Compiler Construction (CC) is
interested in work on processing programs in the most general sense:
analyzing, transforming or executing input that describes how a system
operates, including traditional compiler construction as a special
case.

= IMPORTANT DATES = 
Abstract Submission: November 8, 2020
Full Paper Submission: November 10, 2020
Author Response Period: December 7 - 9, 2020 
Author Notification: December 22, 2020
Artifact Submission: January 5, 2021
AE Notification: January 20, 2021
Final Papers due: January 22, 2021
Conference: February 27 - March 3, 2021

Original contributions are solicited on the topics of interest which
include, but are not limited to:

- Compilation and interpretation techniques, including program
  representation, analysis, and transformation; code generation,
  optimization, and synthesis; the verification thereof
- Run-time techniques, including memory management, virtual machines,
  and dynamic and just-in-time compilation
- Programming tools, including refactoring editors, checkers,
  verifiers, compilers, debuggers, and profilers
- Techniques, ranging from programming languages to
  micro-architectural support, for specific domains such as secure,
  parallel, distributed, embedded or mobile environments
- Design and implementation of novel language constructs, programming
  models, and domain-specific languages

CC is an ACM SIGPLAN conference, and implements guidelines and
procedures recommended by SIGPLAN (https://www.sigplan.org).

Prospective authors should be aware of SIGPLAN’s Copyright
policies. Proceedings will be made available online in the ACM digital
library from one week before to one week after the conference.

Full CfP: https://conf.researchr.org/track/CC-2021/cc-research-papers

ARTIFACT EVALUATION

Authors of accepted papers will be invited to submit their artifacts
for the Artifact Evaluation (AE). The Artifact Evaluation process
begins after the acceptance notification, and is run by a separate
committee whose task is to assess how the artifacts support the work
described in the papers.

To ease the organization of the AE committee, we kindly ask authors to
indicate at the time they submit the paper, whether they are
interested in submitting an artifact.

Papers that go through the Artifact Evaluation process successfully
will receive a seal of approval printed on the papers themselves.

Authors of accepted papers are encouraged, but not required, to make
these materials publicly available upon publication of the
proceedings, by including them as “source materials” in the ACM
Digital Library.

CC AE web page:
https://conf.researchr.org/track/CC-2021/research-artifacts

ORGANIZERS

General Chair:
Aaron Smith - Microsoft / University of Edinburgh

Program Chairs: 
Delphine Demange - Univ Rennes, Inria, CNRS, IRISA
Rajiv Gupta - UC Riverside

Artifact Evaluation Chairs:
Bruno Bodin - Yale-NUS College
Michel Steuwer - University of Glasgow

Web Chair:
Martin Lücke - University of Edinburgh

Steering Committee:
Björn Franke (Chair) - University of Edinburgh
Jose Nelson Amaral - University of Alberta
Christophe Dubach - University of Edinburgh
Sebastian Hack - Saarland University
Manuel Hermenegildo - IMDEA Software Institute and T.U. of Madrid (UPM)
Alexandra Jimborean - University of Murcia
Milind Kulkarni - Purdue University
Louis-Noël Pouchet - Colorado State University
Peng Wu - Futurewei Technologies
Jingling Xue - UNSW Sydney
Ayal Zaks - Intel Corporation and Technion

Program Committee:
Guillaume Baudart - IBM Research
Walter Binder - University of Lugano
Simone Campanoni - Northwestern University
Albert Cohen - Google
Caroline Collange - Inria, Univ Rennes, CNRS, IRISA
Huimin Cui - Institute of Computing Technology, CAS
Christophe Dubach - McGill University
Benoît Dupont de Dinechin - Kalray
Bernhard Egger - Seoul National University
Christine Flood - Red Hat
Laure Gonnord - University of Lyon and LIP
Myoungsoo Jung - KAIST
Andrew Kennedy - Facebook
Dongyoon Lee - Stony Brook University
Christian Lengauer - University of Passau
Xavier Leroy - Collège de France and Inria
Yun Liang - Peking University
Toby Murray - University of Melbourne and Data61
Biswabandan Panda - Indian Institute of Technology Kanpur
Santosh Pande - Georgia Tech
Louis-Noël Pouchet - Colorado State University
Gabriel Rodríguez - Universidade da Coruña
Jan Vitek - Northeastern University
Jingling Xue - UNSW Sydney
Zhijia Zhao - UC Riverside

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and