On Monday, December 19, 2016 at 1:34:01 PM UTC-5, Jens Axel Søgaard wrote:
> Just curious.
Yes, I'm greedy. My case is looking at various daily manipulations of stock
data back to the sixties. A typical textual dump will have date, price, a
manipulated series and usually a column indicating
I'm not sure, but if this is the issue, it's happening somewhere in
the implementation of text%, I believe. In particular, it seems to be
the case that the `insert` method is being called once every 1,000
bytes (with a single string each time). Adding this printf:
(printf "str/snp: ~s\n" (and (s
Just curious.
#lang racket
(for ([x 1000]) (displayln x))
The program above runs very quickly in DrRacket. I can hardly see other
numbers than the final ones.
For this program:
#lang racket
(for ([x 1]) (displayln x))
the first, say, 1000, lines are done in an instant, but
Thanks for the code reference. That will definitely take a while for me to
grok. I will punt with a separate editor window for now and later get
acquainted with the framework text.rkt code.
Thanks again,
John
--
You received this message because you are subscribed to the Google Groups
"Rack
There is probably some performance improvements that could be made to this code:
https://github.com/racket/gui/blob/master/gui-lib/framework/private/text.rkt#L2492-L3240
I've spent some time on this, but your comment about `insert` suggests
that maybe there is another special case in there som
I’m in an situation where Dr. Racket suffices almost perfectly to replace a
Python-based IPython notebook session. The REPL output is graphics and text,
perfect for Dr. Racket.
A problem is that for all but the smallest output, the REPL text output is
simply too lethargic, even compared to t
6 matches
Mail list logo
