[racket-users] Jupyter Racket Kernel - iracket

[Graham Dean]

I’ve been looking to use Racket in a Jupyter notebook and I came across Ryan 
Culpepper’s iracket (https://github.com/rmculpepper/iracket). 

Unfortunately, it doesn’t work with the latest Jupyter system due to a new 
client message (comm_info_request) that isn’t handled.

I’ve made some very simply changes that get iracket working again in Jupyter 
and just in case it’s useful for anyone else it can be found at 
https://github.com/digsci/iracket.

I should really make a pull request (or at least an issue report to the 
original I guess.

Graham 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] On Richard P. Gabriel’s “The Structure of a Programming Language Revolution”

[Sean Kanaley]

> and using version control as the primary source of truth. Reproducibility
is important.

> we got ourselves confused on occasion and the more it happened, the more
it became clear to me that we needed to shift to a more static view

I want to voice what I think is agreement that reliability of the rest of
the universe is important (all that is not "the code right in front of
me"). Correct output is a function of correct input and the correct
function that processes it. So users are intentionally guarded against and
programmers are responsible for config files and source. Everything else
*has* to work. It's extremely confusing (time-wasting) to debug your code
only to later learn the server has the old version of code on it, for
example, or that, god forbid, gcc compiles 2+3 to 2+4 on 13 Aug every year.
The config file is bad enough, but I don't know a solution to that, and
it's under my control in my dev environment. It can definitely get
confusing when the production environment malfunctions due to a config
issue. But, the more confidence the programmer has in their code and the
universe as a whole, the more easily they can just declare "it's probably
the config".

Programming Systems introduce additional mutations of the universe beyond
the source code that effectively undermine the source code. The
"referential transparency" between programmer thought and users' code
execution is lost, unless the programmer manages to perfectly mutate their
thoughts in parallel with the changes to the runtime environment. But we
make mistakes with plain old code, so I'm gonna say, "not happening".

On the other hand, mutation is for efficiency. If there's a case where
refreshing all deployments after a source change takes far too long, a
compromise may be needed. But I don't work in a sufficiently complex
product that would benefit from ditching reliability in favor of
tinkerability, and if it was that complex, I'd probably prefer reliability!

So, I recommend sticking with "Racket AST implies the set of program
outputs".

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[racket-users] Racket PPA updated for v6.12

[Asumu Takikawa]

Hi folks,

The Racket PPA for Ubuntu has been updated to v6.12:

  https://launchpad.net/~plt/+archive/ubuntu/racket

Apologies for the (massive) delay.

It should be available for trusty, xenial, artful, and bionic. I've tested it
with artful.

Please submit any bug reports to

  https://github.com/takikawa/racket-ppa

Cheers,
Asumu

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Heresy 0.3.0 released

[John Berry]

Indeed they are! I had forgotten about the delay and thought perhaps it had 
changed. Thanks!

Sent from my iPhone

> On 30 Apr 2018, at 16.33, Matthew Flatt  wrote:
> 
> At Mon, 30 Apr 2018 14:14:02 +0300, Annaia Berry wrote:
>> Version 0.3.0 of the Heresy programming language has been released,
> 
> That's great!
> 
>> * Note: There seems to be an issue with the package server as it's not
>> rebuilding the hosted docs for me at the moment despite running the recheck
>> twice. I don't know if I'm doing something wrong, someone needs to kick the
>> server, or it's just going to take a moment.
> 
> The docs rebuild once every 24 hours, and the build just completed. Are
> the current docs now as expected?
> 
> -- 
> 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.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] Heresy 0.3.0 released

[Matthew Flatt]

At Mon, 30 Apr 2018 14:14:02 +0300, Annaia Berry wrote:
> Version 0.3.0 of the Heresy programming language has been released,

That's great!

> * Note: There seems to be an issue with the package server as it's not
> rebuilding the hosted docs for me at the moment despite running the recheck
> twice. I don't know if I'm doing something wrong, someone needs to kick the
> server, or it's just going to take a moment.

The docs rebuild once every 24 hours, and the build just completed. Are
the current docs now as expected?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[racket-users] Heresy 0.3.0 released

[Annaia Berry]

Greetings,

Version 0.3.0 of the Heresy programming language has been released,
containing a re-implementation of Holes based on Racket boxes, while
maintaining the same basic API, plus additional support for a "hole-do" DSL
for monadic operations on holes.

Special thanks to Greg Hendershott, for both rackjure, which provided some
of the internals for the new holes implementation, and for his
travis-racket scripts which enabled me to set up CI for Heresy with Travis.

You can find Heresy on Github , or
install with raco pkg install heresy. Docs are available at
http://docs.racket-lang.org/heresy/index.html* or locally after install.

Thanks for your time!
Annaia


* Note: There seems to be an issue with the package server as it's not
rebuilding the hosted docs for me at the moment despite running the recheck
twice. I don't know if I'm doing something wrong, someone needs to kick the
server, or it's just going to take a moment.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[racket-users] final call for papers: Trends in Functional Programming, 11-13 june 2018, Chalmers Campus Johanneberg, Gothenburg - deadline extended -

[p.achten]

   -
 F I N A L   C A L L   F O R   P A P E R S
   -

- deadline extended -
 TFP 2018 ===
 
  19th Symposium on Trends in Functional Programming
   11-13 June, 2018
 Chalmers Campus Johanneberg, Gothenburg
   http://www.cse.chalmers.se/~myreen/tfp2018/index.html

The symposium on Trends in Functional Programming (TFP) is an
international forum for researchers with interests in all aspects of
functional programming, taking a broad view of current and future
trends in the area. It aspires to be a lively environment for
presenting the latest research results, and other contributions (see
below at scope). 

Please be aware that TFP uses two distinct rounds of submissions (see
below at submission details).

TFP 2018 will be the main event of a pair of functional programming
events. TFP 2018 will be accompanied by the International Workshop on
Trends in Functional Programming in Education (TFPIE), which will take
place on June 14.


== SCOPE ==

The symposium recognizes that new trends may arise through various routes. 
As part of the Symposium's focus on trends we therefore identify the 
following five article categories. High-quality articles are solicited in 
any of these categories:

Research Articles:
Leading-edge, previously unpublished research work
Position Articles:
On what new trends should or should not be
Project Articles:
Descriptions of recently started new projects
Evaluation Articles:
What lessons can be drawn from a finished project
Overview Articles:
Summarizing work with respect to a trendy subject.

Articles must be original and not simultaneously submitted for publication 
to 
any other forum. They may consider any aspect of functional programming: 
theoretical, implementation-oriented, or experience-oriented. Applications 
of 
functional programming techniques to other languages are also within the 
scope 
of the symposium.

Topics suitable for the symposium include, but are not limited to:

Functional programming and multicore/manycore computing
Functional programming in the cloud
High performance functional computing
Extra-functional (behavioural) properties of functional programs
Dependently typed functional programming
Validation and verification of functional programs
Debugging and profiling for functional languages
Functional programming in different application areas:
security, mobility, telecommunications applications, embedded
systems, global computing, grids, etc.
Interoperability with imperative programming languages
Novel memory management techniques
Program analysis and transformation techniques
Empirical performance studies
Abstract/virtual machines and compilers for functional languages
(Embedded) domain specific languages
New implementation strategies
Any new emerging trend in the functional programming area

If you are in doubt on whether your article is within the scope of TFP, 
please 
contact the TFP 2018 program chairs, Michał Pałka and Magnus Myreen.


== Best Paper Awards ==

To reward excellent contributions, TFP awards a prize for the best paper 
accepted for the formal proceedings.

TFP traditionally pays special attention to research students, 
acknowledging 
that students are almost by definition part of new subject trends. A 
student 
paper is one for which the authors state that the paper is mainly the work 
of 
students, the students are listed as first authors, and a student would 
present 
the paper. A prize for the best student paper is awarded each year.

In both cases, it is the PC of TFP that awards the prize. In case the best 
paper happens to be a student paper, that paper will then receive both 
prizes.


== Paper Submissions ==

We use EasyChair for the refereeing process. The link to the submission 
page is:

https://easychair.org/conferences/?conf=tfp2018

Authors of papers have the choice of having their contributions formally 
reviewed 
either before or after the Symposium.


== Pre-symposium formal review ==

Papers to be formally reviewed before the symposium should be submitted 
before 
an early deadline and receive their reviews and notification of acceptance 
for 
both presentation and publication before the symposium. A paper that has 
been 
rejected in this process may still be accepted for presentation at the 
symposium, 
but will not be considered for the post-symposium formal review.


== Post-symposium formal review ==

Draft papers will receive minimal reviews and notification of acceptance 
for 
presentation at the symposium. Authors of draft papers will be invited to 
submit 
revised papers based on the feedback receive at the symposium. A 
post-symposium 
refereeing process will then