Hi,
I’ve been using my doctests implementation for years now, and it works
beautifully for me, so I would like to contribute it — either to
guile-lib as (tests doctest) or to guile (maybe (ice-9 doctest)?).
Working code is here:
https://hg.sr.ht/~arnebab/wisp/browse/examples/doctests.scm?rev=tip
Ryan Raymond writes:
> For example, I modified "parse-http-method" and completely removed all error
> throwing capabilities but I am still getting an error thrown from
> within that function.
> (bad-request "Invalid method: ~a" (substring str start end))
>
> I am assuming that the modules are
"Dr. Arne Babenhauserheide" writes:
> this gets rid of a warning in our testsuite (guile-test): it uses load
> but is not marked as non-declarative.
Reviewed by Andy Wingo on IRC ⇒ merged and pushed. Thank you!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
o
Hi Matt,
Matt Wette writes:
> On 3/10/24 6:01 PM, Dr. Arne Babenhauserheide wrote:
> It’s small and it gives an instant improvement when using Guile in Emacs
> orgmode babel sourceblocks that get evaluated on export.
>
> I did look at it. Another solution, I prefer, is ge
Hi,
I just added the remaining tests from the Wisp reader testsuite to the
patch, squashed and rebased it again. The updated patch is attached.
As far as I know, all review comments are addressed and I hope this is
ready to be merged.
Test suite result:
Totals for this test run:
passes:
Hi,
the following patch just adds the note to test-suite/guile-test how to
run it.
This file is referenced in test files, so the instructions it gives
should lead to the right way to run it.
From 097c5e869ebee05d20d8298fdf2a8aa58f2acca0 Mon Sep 17 00:00:00 2001
From: Arne Babenhauserheide
Hi,
this gets rid of a warning in our testsuite (guile-test): it uses load
but is not marked as non-declarative.
The patch:
From 6b7dcf5e77aebe5ad9e22d7cd7c568bc5ed5fccd Mon Sep 17 00:00:00 2001
From: Arne Babenhauserheide
Date: Mon, 11 Mar 2024 01:50:29 +0100
Subject: [PATCH] guile-test:
Hi,
It’s been two months now, did anyone get to review this patch?
It’s small and it gives an instant improvement when using Guile in Emacs
orgmode babel sourceblocks that get evaluated on export.
Best wishes,
Arne
"Dr. Arne Babenhauserheide" writes:
> Hello,
>
> the fo
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
> On Tue, 2023-11-28 at 22:04 +0100, Jonas Hahnfeld wrote:
>> On Sun, 2023-10-29 at 22:34 +0100, Jonas Hahnfeld wrote:
>> > I would like to propose a different approach: It turns out to be
>> > possible to
Hi,
do you know a nice minimal example that shows how to extend Guile with
Rust to get maximum performance for some tasks?
I’m not looking for hints how to speed up Scheme code, or how to do
less. Instead I want to learn how to do those cases where I actually
need some specific algorithm at
Damien Mattei writes:
> On Sat, Jan 20, 2024 at 9:07 PM Dr. Arne Babenhauserheide
> wrote:
> Damien Mattei writes:
> > by keeping the same
> > number of parenthesis, but they are just differents : ( ), { }, [ ]
> > and it allow the use of infix expressions.
Damien Mattei writes:
> i just add a #; support in Scheme+ :
> https://github.com/damien-mattei/Scheme-PLUS-for-Guile
> Scheme+ is an extension syntax to Scheme. It goes in the opposite direction
> of Wisp or Rhombus (based on Racket)
Note that Wisp and Rhombus differ: Wisp is just Scheme
Christina O'Donnell writes:
> On 09/01/2024 07:05, Dr. Arne Babenhauserheide wrote:
>> It’s a new year — any chance for one more look whether adding SRFI-119
>> in Guile is ok to merge?
>
> As a disclaimer, I'm a Scheme newbie, but I think my opinion may have /some/
>
Hi,
I just got the most beautiful feedback on Wisp as a Scheme primer, so I
would like to nag about inclusion of SRFI-119 into Guile again:
»I tend to use [Wisp] as a Scheme primer for colleagues that are used
to Python but want to explore the realms of functional programming
without …
Sorry for the broken message. Re-sending in mu4e produced strange artifacts.
Here’s a clean version:
--
Hello,
the following patch makes Guile suppress the repl-welcome message when
the GUILE_QUIET environment variable is set.
From 5af642cb967942c7cb46b773431a44ceae1e7cbe Mon Sep 17
--==-=-=
Content-Type: multipart/mixed; boundary="=-=-="
--=-=-=
Content-Type: text/plain
Hello,
the following patch makes Guile suppress the repl-welcome message when
the GUILE_QUIET environment variable is set.
--=-=-=
Content-Type: text/x-patch
Content-Disposition: inline;
"Dr. Arne Babenhauserheide" writes:
> Is adding SRFI-119 to Guile good to go?
It’s a new year — any chance for one more look whether adding SRFI-119
in Guile is ok to merge?
Best wishes,
Arne
signature.asc
Description: PGP signature
Hafeez Bana writes:
> The kind of advice you would be giving is:
…
> Alternatively, if there are sysadmin shops that are interested in doing
> this work - please contact me.
>
> 勺 Guix.
Out of interest: Did you already receive applications for this?
If not: ping to all who may have missed
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
>> What do you and others think of this approach, would this be "more"
>> acceptable to land in main?
>
> Ping, any comments on this approach? I built binaries for LilyPond
> 2.25.10 using these patches
ArneBab writes:
> ArneBab writes:
>> I now assigned my copyright in GNU Guile to FSF
> Is the patch now good to go?
Clarification: I don’t actually need someone to push this (I can push).
I just need the go to actually do it (rebase the branch then merge it),
because I don’t want to push my own
"Dr. Arne Babenhauserheide" writes:
> "Dr. Arne Babenhauserheide" writes:
>
>> "Dr. Arne Babenhauserheide" writes:
>>>> OK. I assumed you already emailed ass...@gnu.org the relevant form,
>>>> right? Let us know how it
"Dr. Arne Babenhauserheide" writes:
> "Dr. Arne Babenhauserheide" writes:
>>> OK. I assumed you already emailed ass...@gnu.org the relevant form,
>>> right? Let us know how it goes.
> I now sent a request to be sent the papers to sign to ass...@gnu
Linus Björnstam writes:
> are bound in letrec*. This should also be the case in chez, but chez
> displays an error. Given I have found the chez is never wrong with
> regards to R6RS we can say that guiles behaviour is not conformant
> with r6rs.
…
> What I am saying is: congrats, you found a
Hi,
Linus Björnstam writes:
> When you are not referencing x before defining y everything works as
> you want. There is no, so to say, temporal dependency on how the
> things are bound. When you introduce (display x) before actually
> defining y you force letrec* to bind x to the unspecified
Hi,
while writing a comment to SRFI-245 I think I found an inconsistency in
the Implementation in Guile.
This works:
(define (using-later-variable)
(define x y)
(define y #t)
x)
(using-later-variable)
;; => #t
This still works:
(define (using-later-variable)
(define x y)
(newline)
"Dr. Arne Babenhauserheide" writes:
>> OK. I assumed you already emailed ass...@gnu.org the relevant form,
>> right? Let us know how it goes.
>
> If I read it right, the docs
> https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html
> say that I nee
"Dr. Arne Babenhauserheide" writes:
> I’m attaching the new squashed patch again here and will add the patches
> for the review changes to a second email.
Attached are the promised patches of the additional review changes.
Thank you for yo
Hello Ludo,
Ludovic Courtès writes:
> OK. I assumed you already emailed ass...@gnu.org the relevant form,
> right? Let us know how it goes.
If I read it right, the docs
https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html
say that I need to ask someone to get the papers I can
"Dr. Arne Babenhauserheide" writes:
> diff --git a/doc/ref/srfi-modules.texi b/doc/ref/srfi-modules.texi
> index 0cdf56923..5b82f8070 100644
> --- a/doc/ref/srfi-modules.texi
> +++ b/doc/ref/srfi-modules.texi
> +To execute a file with wisp code, select the language
"Dr. Arne Babenhauserheide" writes:
> Attached is a new squashed patch. I’ll send another email with only the
> commits for the individual changes on top of the original squashed patch
> to avoid tripping up tools that extract diffs.
This is the promised email with just t
Hi,
I did the changes for the review. It took a while (sorry for that) but
it got cleaner as a result (thank you!)
Firstoff: I’d like to assign my copyright to the FSF. I’ll sign the
papers once I receive them. Also I have an Employer disclaimer of rights
on paper for Emacs already, so that
Maxime Devos writes:
>> [...]
>> Can you make it LGPLv3+? It’s a small file anyway.
>
> Only if David A. Wheeler, Alan Manuel K. Gloria and Maxime Devos
> agrees. Otherwise, you still need to include the license text:
I just asked David and Alan, and when I checked the sources I realized
that
Ludovic Courtès writes:
> pukkamustard skribis:
>
>> I've been using SRFI-146
>> (https://srfi.schemers.org/srfi-146/srfi-146.html) for functional
>> mappings. There's a Guile port:
>> https://inqlab.net/git/guile-srfi-146.git/ (also in Guix -
>> guile-srfi-146).
>
> I’m late to the party, but
Josselin Poiret writes:
> Reciprocally, I don't think a simple pull request provides much over
> git-am, except that with `format-patch`, everything is simply text, that
> once sent over email (in a decentralized fashion) can be simply
> responded to and read without relying on complicated
writes:
> You seem to be somewhat upset, but I don't quite understand what
> your gripe is.
If I understood it correctly, they interpret the 'wtf? as expressing
"this is a problem that should be changed" and wanted to say
(equal? '(. a) 'a) should stay #true in Guile and consequently
> "Dr. Arne Babenhauserheide" writes:
>> Ludovic Courtès writes:
>>>> Why should Wisp be a separate package when other SRFIs are made part
>>>> of Guile? Your point about maintenance and evolving applies equally
>>>> to other SRFIs.
>
writes:
> I'd apply Clarke's Razor:"A sufficiently advanced form of malice
> is not distinguishable from stupidity"
I love this! Thank you for sharing!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
signature.asc
Description: PGP signature
Hi,
"Dr. Arne Babenhauserheide" writes:
> Ludovic Courtès writes:
>>> Why should Wisp be a separate package when other SRFIs are made part
>>> of Guile? Your point about maintenance and evolving applies equally
>>> to other SRFIs.
>>
>> Tha
Jannneke Nieuwenhuizen writes:
> In 2014, I wrote patches for Guile to use a debug prompt that GUD can
> work with. The Guile debug patches didn't make it into Guile, but the
> Emacs GUD integration is part of Emacs.
>
>https://lists.gnu.org/archive/html/guile-devel/2014-08/msg4.html
Matt Wette writes:
> On 2/26/23 10:03 AM, Dr. Arne Babenhauserheide wrote:
>> Matt Wette writes:
>>
>>> You can name a file containing Scheme code "foo.js" and "guile foo.js"
>> guile -L . -e '(foo)' -c ''
>>
>> won’t find it.
Matt Wette writes:
> With respect to file extensions, guile does not use file extension:
> You can name a file containing Scheme code "foo.js" and "guile foo.js"
> will execute it.
The module-system uses file extensions: If you
(define-module (foo) #:export (main))
(define (main args)
Hi,
Ludovic Courtès writes:
>> Why should Wisp be a separate package when other SRFIs are made part
>> of Guile? Your point about maintenance and evolving applies equally
>> to other SRFIs.
>
> That’s a good point. Making it available as (srfi srfi-119) would make
> sense I guess. I need to
Hi,
Ludovic Courtès writes:
> FWIW, I think it might be best to keep Wisp as a separate package: that
> allows it to evolve independently of Guile (and possibly more quickly
> :-)), and it might simplify maintenance in some way.
While this reasoning is true for most languages, I don’t think it
Maxime Devos writes:
>> ‘#! ... !#’ comments aren't legacy; they exist to allow putting the
>> shebang in the first line of a script, and to pass additional
>> arguments to the Guile interpreter (see: (guile)The Top of a Script
>> File) (*).
This is awesome, by the way.
It’s what allowed me
Hi Matt,
Please tell me once you know for which patch exactly you need a
WIP-branch.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
signature.asc
Description: PGP signature
Hi,
Thanks to the review of Maxime Devos of my patches to get Wisp into
Guile, Wisp got some improvements that are now released as v1.0.10:
https://www.draketo.de/software/wisp#v1.0.10
Improvements:
- encoding handling only changes the port
- more precise reader adaption (removed side-effects)
Matt Wette writes:
> You may be interested in the load-lang patch I generated a few years ago
> to allow file-extension based loading, in addition to '#lang elisp"
> type hooks.
>
> https://github.com/mwette/guile-contrib/blob/main/patch/3.0.8/load-lang.patch
@Maxime: Is this something you’d
Maxime Devos writes:
> On 16-02-2023 09:03, Dr. Arne Babenhauserheide wrote:
>> Do you mean using it similar to this test?
>>(pass-if "R6RS/SRFI-30 block comment syntax overridden"
>> ;; To be compatible with 1.8 and earlier, we should be able to
Maxime Devos writes:
>> + ;; allow using "# foo" as #(foo).
>> + (read-hash-extend #\# (λ (chr port) #\#))
>
> That's a rather Wisp-specific extension, but it appears you are
> extending things globally. Instead, I propose extending it
> temporarily, with the undocumented
Maxime Devos writes:
>> [...]
>> Which begs an important question: How would you like to be attributed? I
>> plan to also merge this back to the wisp repo and I’d like to attribute
>> you there, too.
>
> You could add a ";; Copyright © 2023 Maxime Devos
> " line next to yours in the file that
ed to not give people ideas on how to circumvent stuff.
> I can elaborate by non-public e-mail if you like.
Thank you! (for redacting) — I hope I’ll never need that :-)
> On 14-02-2023 22:24, Dr. Arne Babenhauserheide wrote:
>> PS: So what’s still missing here is to avoid sett
PS: So what’s still missing here is to avoid setting the locale. Do you
happen to have a hint how to actually do this right?
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
signature.asc
Description: PGP signature
Maxime Devos writes:
> On 04-02-2023 22:35, Dr. Arne Babenhauserheide wrote:
>> Maxime Devos writes:
>>
>>>> This needs an addition to the extensions via guile -x .w — I wrote
>>>> that
>>>> in the documentation. I didn’t want to do that
Maxime Devos writes:
>> This needs an addition to the extensions via guile -x .w — I wrote
>> that
>> in the documentation. I didn’t want to do that unconditionally, because
>> detecting a wisp file as scheme import would cause errors.
>
> If done carefully, I don't think this situations would
Thank you for your review!
Maxime Devos writes:
>> Why add Wisp?
>> For Wisp: it is then available directly wherever Guile is available.
>> This will make it much easier for people to follow tutorials.
>
> I'm not convinced of this argument, because package managers exist, but ...
>
Hi,
Since (language wisp)¹ has been rock stable for years now and is used in
the Guix Workflow Language and supported in the Chickadee and the
Tsukundere game engines, I thought it coud be a good time to merge Wisp
into Guile itself.
So I prepared a patch that adds language/wisp, some texinfo
Jean Abou Samra writes:
> Le 17/01/2023 à 07:21, Dr. Arne Babenhauserheide a écrit :
>> Jean Abou Samra writes:
>>> Thank you for applying the first one nevertheless. I am attaching
>>> patch files for the other two, that should work better.
>> They are a
Hello Jean,
Jean Abou Samra writes:
> Thank you for applying the first one nevertheless. I am attaching
> patch files for the other two, that should work better.
They are applied and pushed now — thank you, and thank you for your patience!
For the eval-when-example I wrote a small change to
Jean Abou Samra writes:
> [[PGP Signed Part:No public key for A3F0F60B893397FE created at
> 2023-01-10T16:51:46+0100 using EDDSA]]
> Le 11/12/2022 à 12:30, Jean Abou Samra a écrit :
>> Aargh, it looks like there is some whitespace mangling at some
>> point between my mail client and debbugs,
Hi,
Jean Abou Samra writes:
> I submitted a few doc patches which are awaiting someone
> to review / push. They should be simple :-) I hope someone
> can have a look.
>
>
> - Document that eq?, eqv? and equal? take any number
> of arguments.
>
>
Ludovic Courtès writes:
> Hi Mike,
>
> Mike Gran skribis:
>
>> On Thu, Sep 15, 2022 at 10:20:26PM -0700, Mike Gran wrote:
>>> I pushed a git branch: wip-modernize-autotools.
>>>
>>> It removes some obsolete tests by presuming we at least have a
>>> C89-compliant C library. It also uses
Jean Abou Samra writes:
> When I did this copyright assignment for Emacs, I recall
> that the procedure was a bit demotivating (the person
> was very friendly, but when you live in an isolated area
> and don't have a printer and you must print the document
> to sign it ...).
It also sounds good
"Dr. Arne Babenhauserheide" writes:
> With the original setting, most benchmarks take around 4-6 MB of
> memory.
> - x1: 4-6 MB
> - x2: 6-9 MB
> - x3: 4-10 MB
> - x4: ~11 MB
> - x32: 4-74 MB
Additional support to the comment by Andy about heap size:
racket -e
Aleix Conchillo Flaqué writes:
> On Thu, Jun 23, 2022 at 3:20 PM Maxime Devos wrote:
>
> Aleix Conchillo Flaqué schreef op do 23-06-2022 om 14:13 [-0700]:
> >
> https://community.spotify.com/t5/Spotify-for-Developers/API-Authorization-header-doesn-t-follow-HTTP-spec/m-p/5397381#M4917
> > >
Aleix Conchillo Flaqué writes:
> On behalf of the Fibers team, I am excited to announce Fibers 1.1.1.
>
> Fibers is a lightweight concurrency facility for Guile that supports
> non-blocking input and output, millions of concurrent threads, and Concurrent
> ML-inspired communication primitives.
Stefan Israelsson Tampe writes:
> After optimising the hashtable implementation I conclude the following,
> 1. + 0.25s 10M lookups in small hashtable (0.36s for guiles current)
> 2. + 6X faster for a large table scanning numbers
What do you mean by "large taable scanning numbers"? (I don’t
Jean Abou Samra writes:
> For your information:
>
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1250
That’s awesome — thank you!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
signature.asc
Description: PGP signature
Jean Abou Samra writes:
>>> There is also a felicitous feedback effect in that because the
>>> baseline compiler is much smaller than the CPS compiler, it takes less
>>> time to macro-expand —
>>> https://wingolog.org/archives/2020/06/03/a-baseline-compiler-for-guile
>
> As far as I
Maxime Devos writes:
> Jean Abou Samra schreef op wo 09-03-2022 om 00:31 [+0100]:
>> In summary, the less Guile optimizes, the faster LilyPond runs. Is that
>> something expected?
>
> I don't think so, but I don't have a clue how this happens ...
Do I understand it correctly that Lilypond has
Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library"
writes:
> [[PGP Signed Part:Good signature from 91C9C33D2C61ACDB Jonas Hahnfeld
> (trust undefined) created at
> 2021-11-19T13:18:31+0100 using RSA]]
> Am Sonntag, dem 10.10.2021 um 18:22 +0200 schrieb Jonas
Aleix Conchillo Flaqué writes:
> Using INADDR_ANY instead of INADDR_LOOPBACK makes it convenient when
> starting the web server inside containers without the need to having to
> specify INADDR_ANY all the time. This is the default in most libraries
> and languages.
>
> This doesn't break
Aleix Conchillo Flaqué writes:
> * doc/ref/web.texi (Web Server): need quasiquote to in order to evaluate
> AF_INET6.
> ---
> -(run-server handler 'http '(#:family AF_INET6 #:port 8081))
> +(run-server handler 'http `(#:family ,AF_INET6 #:port 8081))
Looks good! Thank you! (this would have
Greg Troxel writes:
> [[PGP Signed Part:Signature made by expired key 1FDA7AE8098ED60E Gregory D.
> Troxel (low security, at work) ]]
>
> Maxime Devos writes:
>
>> Maybe the IPV6_V6ONLY (see the ipv6(7) man page) is relevant here.
>> Alternatively, you could run two servers in parallel: one
Chris Vine writes:
> On Wed, 19 Jan 2022 13:44:13 +
> Chris Vine wrote:
>> On Wed, 19 Jan 2022 13:07:33 +
>> Chris Vine wrote:
>> [snip]
>> > As I understand it, with linux IPv6 sockets are dual stack capable, and
>> > in earlier kernel versions this was be enabled by default. I
Hi,
with both fibers server and (web server) there is a split between IPv4
and IPv6:
IPv4:
(fibers:run-server handler-with-path #:family AF_INET #:port port #:addr
INADDR_ANY)
(run-server handler-with-path 'http `(#:host "localhost" #:family ,AF_INET
#:addr ,INADDR_ANY #:port
Olivier Dion via "Developers list for Guile, the GNU extensibility library"
writes:
> On Tue, 21 Dec 2021, Blake Shaw wrote:
>> Tim Van den Langenbergh writes:
>>> That sounds like a good idea, though I wonder what the best way to organise
>>> it would be.
>>>
>>> IRC, Mattermost, and
Jean Abou Samra writes:
> make it to the main branch. If the current maintainers
> need to drop their activity, it would be nice if
> they could share maintainership so that at least
> bug fixes can be applied.
I got the requirements for copyright assignment in place two weeks ago,
so I could
Hi,
the attached patch adds a small section to the website that I’ve been
missing a few times already, so I thought I’ll just add it :-)
The patch is for https://git.savannah.gnu.org/cgit/guile/guile-web.git/
From 11da5a6eacb0052e66065bf39a34c55bd496b431 Mon Sep 17 00:00:00 2001
From: Arne
Andy Wingo writes:
> Anyway, thoughts welcome. Happy hacking :)
This sounds great — thank you!
I personally would already be happy if I could start by replacing my
small biwascheme utility by guile-based webassembly:
https://www.draketo.de/software/matrikellanguage.scm
Currently used via
Hello Gregg,
"Gregg Sangster" writes:
> I've rebased the wip-elisp branch on top of commit
> 449f50dd84a081aea16ef678e32bf37abe429ff6 (git describe:
> v3.0.4-64-g33232cb5c4). It's published here:
>
> https://git.sr.ht/~g20r/guile
I’m not a Guile core developer, but I think that this is
Stefan Israelsson Tampe writes:
> (define-syntax-rule (letec f)
> (let/ec x (f x
>
> Actually lead to similar speeds as python3.
Please keep in mind that this is math. There are parts of Python that
are heavily optimized, for example reading strings from disk. Guile will
likely have a
Stefan Israelsson Tampe writes:
> I have continued to debug python for guile 3.1 and I am now getting much
> less warnings and also I can run test cases and it looks good. Tip, To run
> unit tests one can do from the module directory in the dist
>
> python
Hi,
I’d like to ask again if anyone can help the Lilypond folks with setting
optimization settings for code they compile from lilypond-files:
> Are there ways to improve this? For example sticking to the baseline
> compiler (as described in the wingolog:
>
Knut Petersen:
>> I wonder what the Carver MSDM score would look like. Searching the archives,
>> it's seemingly become an informal standard for large-project stress tests.
>
> Carver MDSM compiled with guile master and lilypond master: 19.7 seconds
> Carver MDSM compiled with guile 1.8 +
ieb Thomas Morley
> :
>>
>> Am Do., 11. März 2021 um 22:47 Uhr schrieb Dr. Arne Babenhauserheide
>
>> > Do you already have results?
>>
>> Currently my regular job eats up all my time.
>> Probably I'll find some free time at upcoming weekend, not sure tho
Hi,
due to the reader-rewrite, I asked in the lilypond-list for testing,
because they are likely the strongest power-user of the reader.
Han-Wen Nienhuys checked performance in the benchmark suite:
> $ cat ../bench.ly
> #(define (microseconds)
> (let* ((t (gettimeofday))
> (us (/ (cdr t)
ort-trust-value
0.00 7.82 0.00 remove
0.00 0.02 0.00 anon #x7a24b0
---
Sample count: 3820
Total time: 62.773351245 seconds (2.013414284 seconds in GC)
(I see here that the GC time during actual trust calculation is much
lower than I had expected)
I hope they help! (you’ll
Hi Guilers,
There’s one more thing for the Potluck:
I started doing some code-catas in Guile wisp:
https://www.draketo.de/software/wisp-code-katas
Liebe Grüße,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
signature.asc
Description: PGP signature
Hi Linus,
Linus Björnstam writes:
> I had a look and there is quite a lot you can do. Just out of
> curiosity: how much is GC time? You are generating a lot of
> intermediate data. Instead of vector-append! maybe use something like
> the new vectorlist srfi? If you show me a flame graph and give
I’d like to contribute a basic implementation of the Web of Trust in
Freenet that provides spam-detection without centralized control:
https://hg.sr.ht/~arnebab/wispwot/browse/wispwot/wispwot.scm
Currently this takes 70s to calculate aggregated trust scores on 300k
trust edges.
I hope to get
Alex Sassmannshausen writes:
> I would love to participate by cheating a little and submitting a new
> release of Guile Hall, which is overdue and should happen between 1 and
> 6 March.
\o/
thank you!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
Marc Nieper-Wißkirchen writes:
>>> While I have been contributing to R7RS-large, I have to agree with you
>>> to some extent. Most of the SRFIs that have been voted into R7RS-large
>>> or are to be submitted for it don't have the quality of the R6RS or
>>> R7RS(-small) specifications
>
>>
92 matches
Mail list logo
