[racket-users] CFP: PLOS '21: 11th Workshop on Programming Languages and Operating Systems

[Eric Eide]

Do you use Racket in the implementation of operating systems or "OS-like"
systems?  Consider submitting a short paper about your work to the PLOS '21
workshop!  Papers are due on August 6, about one month from now.

Eric.

---

CALL FOR PAPERS

 11th Workshop on Programming Languages and Operating Systems
  (PLOS 2021)

   October 25, 2021
Online

https://plos-workshop.org/2021/

Sponsored by ACM SIGOPS
 In conjunction with SOSP 2021
https://sosp2021.mpi-sws.org/index.html

Paper submission deadline:  August 6, 2021
Notification of acceptance:  September 3, 2021
Final papers due:   September 24, 2021
Workshop: October 25, 2021


Historically, operating system development and programming language development
went hand-in-hand.  Challenges in one area were often approached using ideas or
techniques developed in the other, and advances in one area enabled new
capabilities in the other.  Today, although the systems community at large
retains an iron grip on C, modern programming language ideas continue to spark
innovations in OS design and construction.  Conversely, the systems field
continues to provide a wealth of challenging problems and practical results
that should lead to advances in programming languages, software designs, and
idioms.

This workshop will bring together researchers and developers from the
programming language and operating system domains to discuss recent work at the
intersection of these fields.  It will be a platform for discussing new
visions, challenges, experiences, problems, and solutions arising from the
application of advanced programming and software engineering concepts to
operating systems construction, and vice versa.

Suggested paper topics include, but are not restricted to:

  * critical evaluations of new programming language ideas in support of OS
construction
  * domain-specific languages for operating systems
  * type-safe languages for operating systems
  * the design of language-specific unikernels
  * language-based approaches to crosscutting system concerns, such as
security and run-time performance
  * language support for system verification, testing, and debugging
  * synthesis of OS code
  * static/dynamic configuration of operating systems
  * static/dynamic specialization within operating systems
  * the use of OS abstractions and techniques in language runtimes
  * experience reports on applying new language techniques in commercial OS
settings

AGENDA

The workshop will be a highly interactive event with an agenda designed to
promote focused and lively discussions.  Part of the workshop program will be
based on paper presentations.  PLOS welcomes research, experience, and position
papers; papers describing industrial experience are particularly encouraged.
The set of accepted papers will be made available to registered attendees in
advance of the workshop.  Participants should come to the workshop prepared
with questions and comments.

SUBMISSION GUIDELINES

All papers must be written in English and should be formatted in the two-column
ACM article style (, using the
options sigplan,10pt).  The CCS Concepts, Keywords, and ACM Reference Format
sections are not required in submissions.  Submissions are single blind: author
names and affiliations should be included.

Submissions must not be more than six (6) pages in length, using 10-point font.
The bibliography does not count towards the page limit.  The page limit will be
strictly enforced, and shorter papers are encouraged. Papers must be submitted
in PDF format via the workshop website. They will be reviewed by the workshop
program committee and designated external reviewers. Papers will be evaluated
based on technical quality, originality, relevance, and presentation.

By default, accepted papers will be published electronically in the ACM Digital
Library. The authors of accepted papers to be included in the ACM Digital
Library will be required to sign ACM copyright release forms.  The publication
of a paper in the PLOS workshop proceedings is not intended to replace future
conference publication.

PROGRAM COMMITTEE

Anton Burtsev, University of California, Irvine
Pierre-Evariste Dagand, Universite de Paris (chair)
Michael Homer, Victoria University of Wellington
Faria Kalim, Apple Inc
Jeehoon Kang, KAIST
Antoine Kaufmann, MPI for Software Systems
Hui Lu, SUNY Binghamton
Gustavo Petri, Arm Research
Clement Pit-Claudel, Massachusetts Institute of Technology
Linhai Song, Pennsylvania State University
Alain Tchana, Ecole Normale Superieure de Lyon
Chia-Che 

Re: [racket-users] Re: [ANN] megaparsack 1.4 — support for user-defined parser state

[Siddhartha Kasivajhula]

The lookahead feature

you've
added is precisely what I was missing when I tried megaparsack, although I
was able to work around the need for it with some hacks. Excited to give it
another try!


On Sun, Jul 4, 2021 at 12:21 PM Alexis King  wrote:

> Addendum: the docs are now built, so you can read more at these two links:
>
>- https://docs.racket-lang.org/megaparsack/state.html
>-
>
> https://docs.racket-lang.org/megaparsack/reference.html#%28part._parser-parameters%29
>
>
> On Sun, Jul 4, 2021 at 2:21 AM Alexis King  wrote:
>
>> Hi all,
>>
>> As some of you may know, I am the maintainer of the Megaparsack
>>  package, a
>> Parsec-style parser combinator library. Though it’s mostly been in
>> maintenance mode for some time, the latest release adds a significant new
>> feature: *user-defined parser state*. This closes the main expressivity
>> gap Megaparsack has historically had relative to Parsack (though Parsack
>> continues to be more performant).
>>
>> As a quick overview to pique your interest, Megaparsack 1.4 provides a
>> new abstraction called a *parser parameter*. Parser parameters are
>> similar to ordinary Racket parameters, but their state is associated with a
>> parsing context rather than with a thread. Their interface should already
>> look familiar to Racketeers, so here is an example that uses parser
>> parameters to implement an indentation-sensitive syntax:
>>
>> (define current-indent (make-parser-parameter 0))
>>
>> (define skip-current-indent/p
>>   (do [cols <- (current-indent)]
>>   (repeat/p cols (char/p #\space
>>
>> (define markdown-like-list/p
>>   (do (string/p "* ")
>>   [blk <- block/p]
>>   [cols <- (current-indent)]
>>   [blks <- (parameterize/p ([current-indent (+ cols 2)])
>>  (many/p block/p))]
>>   (pure (cons blk blks
>>
>> Modifications to parser parameters are automatically reverted when the
>> parser backtracks past the point of modification, which allows them to be
>> used for accumulating information during parsing even if the current parse
>> branch is tentative. To illustrate, note that this example results in 10
>> rather than 15:
>>
>> (define current-count (make-parser-parameter 0))
>>
>> (define (increment/p n)
>>   (do [count <- (current-count)]
>>   (current-count (+ count n
>>
>> > (parse-string
>>(do (or/p (try/p (do (string/p "!") (increment/p 5) eof/p))
>>  (do (string/p "!!") (increment/p 10) eof/p))
>>(current-count))
>>"!!")
>> (success 10)
>>
>> I generally don’t post about releases to this list, but I happen to know
>> Megaparsack has at least a few active users, and this is the first major
>> update in a long while, so I figured I’d give a heads-up. If you’ve counted
>> the library out in the past for missing this feature, consider giving it
>> another look. And if you’re interested in learning more, the gory details
>> are described in the documentation, along with some additional examples (at
>> the time of this writing, pkg-build hasn’t rebuilt the docs just yet, but
>> that should be resolved with tomorrow’s daily refresh).
>>
>> Happy parsing,
>> Alexis
>>
> --
> 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/CAA8dsafQt%2BCtXPVFKuTYC1ZShC3%3DZgzNBEzfe7_bH67sYCJMCg%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/CACQBWFnh%2B4DAa%2Bdze%2BADXfKXswtjkMQqkPy0ZV3aFm_2vGrTeQ%40mail.gmail.com.

Re: [racket-users] parenthesis colours

[Robby Findler]

I chose the paren default color to deemphasize the parentheses. I'm not
sure that emphasizing them would be a good change. I can see how, on some
monitors, the deemphasis might have been too much but I'm not quite ready
to change that design choice!

Robby


On Mon, Jul 5, 2021 at 11:07 AM Hendrik Boom  wrote:

> On Mon, Jul 05, 2021 at 07:52:39AM -0500, Robby Findler wrote:
> > Glad to hear it! Sorry the defaults looked bad.
>
> They look pretty enough.  They just aren't useful.
> I turned the parentheses bright yellow.
> Unless yellow comflicts with some other use of the same colour,
> may I recommend it ne made default?
>
> -- hendrik
>
> >
> > Robby
> >
> > On Mon, Jul 5, 2021 at 7:02 AM Hendrik Boom 
> wrote:
> >
> > > On Sun, Jul 04, 2021 at 08:18:24AM -0500, Robby Findler wrote:
> > > > If you go to the preference dialog, choose "Colors", and then choose
> > > > "Racket" you should be able to adjust each color independently.
> > > >
> > > > There are also some themes for DrRacket in dark mode that have
> different
> > > > color schemes; I think Tol's is installed by default and there are
> more
> > > on
> > > > the pkg server.
> > > (offlist)  Thank you.  Much. much better now.
> > >
> > > -- hendrik
> > > >
> > > > hth,
> > > > Robby
> > > >
> > > >
> > > > On Sun, Jul 4, 2021 at 7:26 AM Hendrik Boom 
> > > wrote:
> > > >
> > > > > I use drracket in what I call night mode -- dark backgroun and
> bright
> > > > > letters.
> > > > > It's easier on the eyes,
> > > > > except when I have to see parentheses.
> > > > > They are presented in a dark shade of red.
> > > > > Given how crucial parentheses are in Racket, this is an obstacle,
> > > > > especially when the error-reporting mechanism highlights a part of
> the
> > > > > code it thinks is in error -- using red highlighting, obscuring the
> > > > > possibly unbalanced parentheses completely.
> > > > >
> > > > > Is it possible to set parenthese to be some other colour, such as,
> say,
> > > > > a bright green or white?
> > > > >
> > > > > -- hendrik
> > > > >
> > > > > --
> > > > > 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/20210704122648.hbztacmpzcjvc3hd%40topoi.pooq.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/CAL3TdOP7m7MsbRw8MDjevLuB5z9TDDp_AZCL5suTQbNJb9dujQ%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/20210705160659.fbyng6drfono7cow%40topoi.pooq.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/CAL3TdOOOmZK0U8kDKeK0eaabD_D-2W2%3D1zUH9vSxwNHLrSgWmA%40mail.gmail.com.

Re: [racket-users] parenthesis colours

[Hendrik Boom]

On Mon, Jul 05, 2021 at 07:52:39AM -0500, Robby Findler wrote:
> Glad to hear it! Sorry the defaults looked bad.

They look pretty enough.  They just aren't useful.
I turned the parentheses bright yellow.
Unless yellow comflicts with some other use of the same colour,
may I recommend it ne made default?

-- hendrik

> 
> Robby
> 
> On Mon, Jul 5, 2021 at 7:02 AM Hendrik Boom  wrote:
> 
> > On Sun, Jul 04, 2021 at 08:18:24AM -0500, Robby Findler wrote:
> > > If you go to the preference dialog, choose "Colors", and then choose
> > > "Racket" you should be able to adjust each color independently.
> > >
> > > There are also some themes for DrRacket in dark mode that have different
> > > color schemes; I think Tol's is installed by default and there are more
> > on
> > > the pkg server.
> > (offlist)  Thank you.  Much. much better now.
> >
> > -- hendrik
> > >
> > > hth,
> > > Robby
> > >
> > >
> > > On Sun, Jul 4, 2021 at 7:26 AM Hendrik Boom 
> > wrote:
> > >
> > > > I use drracket in what I call night mode -- dark backgroun and bright
> > > > letters.
> > > > It's easier on the eyes,
> > > > except when I have to see parentheses.
> > > > They are presented in a dark shade of red.
> > > > Given how crucial parentheses are in Racket, this is an obstacle,
> > > > especially when the error-reporting mechanism highlights a part of the
> > > > code it thinks is in error -- using red highlighting, obscuring the
> > > > possibly unbalanced parentheses completely.
> > > >
> > > > Is it possible to set parenthese to be some other colour, such as, say,
> > > > a bright green or white?
> > > >
> > > > -- hendrik
> > > >
> > > > --
> > > > 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/20210704122648.hbztacmpzcjvc3hd%40topoi.pooq.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/CAL3TdOP7m7MsbRw8MDjevLuB5z9TDDp_AZCL5suTQbNJb9dujQ%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/20210705160659.fbyng6drfono7cow%40topoi.pooq.com.