Hello guile-devel,
Bumping this simple documentation bug fix to (ice-9 getopt-long).
~ Vijay
>From 852d9eee636a0be61ea3e0fab88a5780971d33c2 Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Wed, 17 Aug 2022 09:13:18 -0400
Subject: [PATCH] doc: fix documented keyword argument default to ma
his would take way too long for me, so I'll leave this up to
another contributor in the future. Would be a great first contribution!
> The rest looks great to me!
>
> Could you send an updated patch?
I've attached the updated patch.
~ Vijay
>From 0b1b46123a62c2c65dd58805592d4
Hello guile-devel,
Looking for a review and merge of this patch if possible!
~ Vijay
Hello,
I've attached a simple documentation bugfix patch for getopt-long,
`#:stop-at-first-non-option' defaults to #f, not #t.
~ Vijay
From 852d9eee636a0be61ea3e0fab88a5780971d33c2 Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Wed, 17 Aug 2022 09:13:18 -0400
Subject: [PATCH
of the patches that fixes that typo. Assuming that no
changes are required for the null bytes comments.
Hoping this can get merged soon!
~ Vijay
>From 6f287255456dbefb75a1c2242904c8f0046ad5bb Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Thu, 20 Jan 2022 22:19:25 -0500
Subject: [PATCH 1
> Could you send this patch to bug-gu...@gnu.org? That way it gets
> registered in the bug tracker, and a maintainer can apply it when they
> are able to.
Looks like the typo fix patch was committed to main by lloda, thanks! I
have sent the rest of my patches to bug-guile, I wasn't aware of the
> This is *really* good. Pull in all the separate pieces and how they
> fit together. Great job!
Thank you! More coming soon, hopefully :)
~ Vijay
> I'd like to have continuable exceptions covered, though
>
> Those are the main departure of Guile from more widespread exception
> handling solutions and as far as I can tell something similar is available
> only in Common Lisp so drawing experience/intuition from other languages is
> more diffic
> This nice funktional interface runs with no measurable speed overhead
> compared to old cases. Also this is essentially python generators and
> this code runs in 0.3s where a python generator example runs in 0.5s,
> using delimited continuation we are talking about 6-7s.
That's quite amazing!
> Awesome blogpost. Very clean and fun to read! Is this generated with
> static website generator for org-mode?
That's great to hear! Appreciate the feedback, I'm glad the writing
style is working, will try to maintain it.
The website is a static website that is implemented in Guile, but does
n
Hello!
I have attached a patch that fixes the simple example of defining (unless
...) with a macro.
~ Vijay
>From 42c830b3d14106d18df154d9a34fff2a9ffa532e Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Tue, 15 Feb 2022 17:36:08 -0500
Subject: [PATCH] Typo fix: Use correct variable name
dsm...@roadrunner.com writes:
> The Guile Manual is a Reference. Mainly a Reference. There are some
> tutorial-like things in it, and some explanations, but not much.
>
> It really would be good to have more non-reference documentation.
I fully agree, if possible, under the Guile documentation wo
> Is there any interest/possibility to have such a cookbook hosted
> within the Guile official documentation (as it is for Guix) ?
I personally think that a Cookbook should be an independent effort, with
links from the Guile Manual if possible. This would lighten the load on
the maintainers, and a
e
> even if they are modified. Thus, modifications to str show up in
> the new string, and vice versa.
That seems like surprising behavior to me (when you don't know that they
are shared). In case sharing is important, one can add a
`string-split-substring/shared' procedure?
RC, others find it useful as well. The patch is attached.
~ Vijay
>From 44ba1874d32e188fdd999e113781548ab2b128fa Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Sat, 12 Feb 2022 22:00:57 -0500
Subject: [PATCH] Add string-split-substring
* /ref/api-data.texi: Added documentation
* modul
This is exciting work, thanks for sharing! Maybe non-continuable
exceptions could be based on pausing continuations.
~ Vijay
not being used anywhere in the process.
I have attached the edited patch, and the new R7RS patch.
~ Vijay
>From c6be127b4818d43a0244592c18a52de113d3ff08 Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Thu, 20 Jan 2022 22:19:25 -0500
Subject: [PATCH 1/2] Allow utf8->string, utf16->string,
27; exception without attributing
> it to 'utf8->string' (untested).
Switched to scm_to_unsigned_integer, that does bounds checks. This is
what `substring' does.
The updated patch is attached.
~ Vijay
>From 61b4b444eec1a8825d54604cbcb5a68bcfa9cef5 Mon Sep 17 00:00:00 2001
From: V
t #:optional (end (bytevector-length bv)))
> (utf8->string (%subbytevector bv start end)
Would appreciate any thoughts and feedback.
~ Vijay
>From 695c2a6189458a292819df8fba659ea488dc0b4e Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Thu, 20 Jan 2022 22:19:25 -0500
Su
> I haven't really looked closely at the documentation or code,
> but the structure of the patch seems fine now
That's good to hear, awaiting code review then!
> , except perhaps:
>
>> "Software"), to deal in the Software without restriction, including
>
> Unicode has been a thing now since quite
ed by the maintainer,
> not the contributor.
Sounds good.
Attached is the latest version of the patch.
~ Vijay
>From b55a1e2295013ba6a9e0a1a98d188c17a0fd7058 Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Tue, 18 Jan 2022 20:52:08 -0500
Subject: [PATCH] Added srfi-2
on Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Tue, 18 Jan 2022 20:52:08 -0500
Subject: [PATCH] Added srfi-214: flexvectors
Included code, documentation, and tests
---
doc/ref/api-data.texi | 842 -
doc/ref/srfi-modules.texi | 6 +
module/Makef
so at most a ‘© FSF’ line could
> be added (*), however, the copyright line ‘© Adam Nelson’ would need to
> remain, otherwise the copyright lines are misleading.
>
> (*) This assumes you did copyright assignment to the FSF, otherwise
> ‘© Vijay Marupudi’.
That's fair, thanks for
lson/scheme-flexvectors/blob/master/LICENSE>
I have attached the updated patch.
~ Vijay
>From ec49b052809bbe44ee47765db0dd887313702dcc Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Tue, 18 Jan 2022 20:52:08 -0500
Subject: [PATCH] Added srfi-214: flexvecto
.
~ Vijay
>From f52164919a50600960aad2df323a3a3f51cf1427 Mon Sep 17 00:00:00 2001
From: Vijay Marupudi
Date: Tue, 18 Jan 2022 20:52:08 -0500
Subject: [PATCH] Added srfi-214: flexvectors
---
module/Makefile.am | 1 +
module/srfi/srfi-214.scm | 730 +++
strategy.
~ Vijay
On 8/9/21 1:24 PM, Maxime Devos wrote:
> Vijay Marupudi schreef op zo 08-08-2021 om 23:02 [-0500]:
>> Thank you for your responses Taylan and Maxime!
>>
>> My initial reaction to the concern about multithreaded code is similar
>> to Taylan. I'm not
Thank you for your responses Taylan and Maxime!
My initial reaction to the concern about multithreaded code is similar
to Taylan. I'm not sure if Guile has multithreading concepts built into
the compiler. If so, one can only check the length again after a mutex.
Appreciate the malloc, realloc, an
custom C extension vector and allow me to use other
vector-* functions.
Ideally, this would use libc's `realloc` to make the resize
quick, so that it can avoid data copying whenever possible.
Regards
Vijay Marupudi
PhD Student in Human Centered-Computing
Georgia Tech
28 matches
Mail list logo
