Hi,
I've been using Typed Racket in the last few months and it has been an
interesting experience.
However, there are a few helpful features of "normal" Racket that are not
yet available in Typed Racket.
One of them is the ability to use #:constructor-name in struct type
definitions.
I used
Ah, that’s my package, and that issue is my mistake. I had a version exception
for 6.2, but I was missing a version exception for 6.2.1. It should work on
6.2.1 now. Try updating alexis-collections (or uninstalling/reinstalling it),
and it pull the right version. Thanks for the report!
Alexis
Hi,
On Thu, Nov 19, 2015 at 11:36 AM, WarGrey Gyoudmon Ju wrote:
> 1. define structs in untyped racket;
> 2. (require/typed/provide) it with #:constructor-name option.
>
>
Thanks for the suggestion.
Meanwhile, I thought about a different approach. Here is one example:
I installed the package alexis-collections via DrRacket. The build process
reported problems with an unbound identifier, and after investigating I found
that my installation's racket/function module is missing a couple of things
that are in the current version on GitHub. However, DrRacket
Brian Adkins wrote on 11/19/2015 07:08 PM:
The example that provided the initial motivation is extremely simple - process
45M+ text records with some minor transformations (including computing a couple
soundex values on first/last names). Racket came in at 2.4x faster than Ruby,
but still CPU
On Thursday, November 19, 2015 at 5:37:12 PM UTC-5, johnbclements wrote:
> > Any thoughts from folks that are FFI'ing from/to Racket and/or using a
> > second language in the same system as Racket ?
>
> My “thoughts" are more along the lines of cheerleading. I worked on Hygiene
> for Rust, and
On Thursday, November 19, 2015 at 7:45:45 PM UTC-5, Neil Van Dyke wrote:
> Brian Adkins wrote on 11/19/2015 07:08 PM:
> > The example that provided the initial motivation is extremely simple -
> > process 45M+ text records with some minor transformations (including
> > computing a couple soundex
On Thursday, November 19, 2015 at 6:25:19 PM UTC-5, Matthias Felleisen wrote:
> Brian,
>
> -- when you say "raw speed", do you need "Fortran" level speed for numerical
> algorithms or just "somewhat faster than Racket, almost close to C"? If it's
> the latter, Rust may work out for you.
I
On Fri, Nov 20, 2015 at 3:27 AM, Antonio Menezes Leitao <
antonio.menezes.lei...@ist.utl.pt> wrote:
> Hi,
>
> On Thu, Nov 19, 2015 at 11:36 AM, WarGrey Gyoudmon Ju <
> juzhenli...@gmail.com> wrote:
>
>> 1. define structs in untyped racket;
>> 2. (require/typed/provide) it with #:constructor-name
On 2015-11-19 09:11:08 +, Antonio Menezes Leitao wrote:
>So, my questions are:
>1. Are there any plans to support #:constructor-name in Typed Racket?
I haven't tried to implement support for it, but I can't think of anything off
the top of my head that would make it difficult. I
Outstanding, thank you.
On Thursday, November 19, 2015 at 2:52:52 PM UTC-5, Alexis King wrote:
> Ah, that’s my package, and that issue is my mistake. I had a version
> exception for 6.2, but I was missing a version exception for 6.2.1. It should
> work on 6.2.1 now. Try updating
The more I dig into Racket, the more I like it. It seems like a perfect fit for
both my personality and the type of applications I am, and will be, writing.
For the vast majority of what I need to do, it's a great fit.
I do occasionally encounter a need for raw speed, so I'm looking for a
Brian,
-- when you say "raw speed", do you need "Fortran" level speed for numerical
algorithms or just "somewhat faster than Racket, almost close to C"? If it's
the latter, Rust may work out for you.
-- when you say you need many cores for your computations. That sounds like
very-raw
I appreciate all the responses. Time to do some reading and experimenting. At
this point I've managed to read files and use regex to pull data into new
variables or parameters I've set up, but I haven't gotten to the point of
actually reading in racket data structures, so this gives me an angle
1. define structs in untyped racket;
2. (require/typed/provide) it with #:constructor-name option.
On Thu, Nov 19, 2015 at 5:11 PM, Antonio Menezes Leitao <
antonio.menezes.lei...@ist.utl.pt> wrote:
> Hi,
>
> I've been using Typed Racket in the last few months and it has been an
> interesting
Yes, I like the idea of #lang info(#lang setup/infotab) which is highly
constrained, and it is an out-of-box solution.
It's better to have a (get-info/file filename.rkt) as an alternative to
(get-info/full infodir-path).
On Thu, Nov 19, 2015 at 7:32 AM, Neil Van Dyke
On Thursday, November 19, 2015 at 9:56:01 PM UTC-5, gustavo wrote:
> > I did *some* hand optimizing. Here's the code for the soundex and some
> > string helper functions I created:
> >
> > https://gist.github.com/lojic/1deba97f2e2eb2fe3fc0
> >
>
> I'm optimistic and I think that there is still
> I did *some* hand optimizing. Here's the code for the soundex and some string
> helper functions I created:
>
> https://gist.github.com/lojic/1deba97f2e2eb2fe3fc0
>
I'm optimistic and I think that there is still some room for
micro-optimizations (for example, replace the set!'s, but I didn't
On Thursday, November 19, 2015 at 11:08:07 PM UTC-5, Brian Adkins wrote:
> On Thursday, November 19, 2015 at 9:56:01 PM UTC-5, gustavo wrote:
> > > I did *some* hand optimizing. Here's the code for the soundex and some
> > > string helper functions I created:
> > >
> > >
I have a related question. I turned on error trace using the command line Robby
suggested, but it doesn't give me a trace, but rather just the call point and
error function. Here is an example, the trace should be f -> gg -> g -> hh ->
h then bang, the error. But instead Racket shows me f
On Thursday, November 19, 2015 at 11:18:16 PM UTC-5, Brian Adkins wrote:
> On Thursday, November 19, 2015 at 11:08:07 PM UTC-5, Brian Adkins wrote:
> > On Thursday, November 19, 2015 at 9:56:01 PM UTC-5, gustavo wrote:
> > > > I did *some* hand optimizing. Here's the code for the soundex and some
21 matches
Mail list logo