From: Andy Wingo <wingo@pobox.com>
To: taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer")
Cc: guile-user@gnu.org
Subject: Re: Bytestructures: a "type system" for bytevectors
Date: Mon, 20 Jun 2016 15:24:46 +0200 [thread overview]
Message-ID: <87y460gfhd.fsf@pobox.com> (raw)
In-Reply-To: <87r3mkg2iy.fsf@T420.taylan> ("Taylan Ulrich \"Bayırlı/Kammer\""'s message of "Sun, 30 Aug 2015 18:32:53 +0200")
On Sun 30 Aug 2015 18:32, taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
> https://github.com/taylanub/scheme-bytestructures
>
> (I don't endorse GitHub, but I gave in after Gitorious went down.)
>
> I had started working on this project around two years ago but it had a
> pretty strange and complex API, an unreadable README, high overhead for
> something you might want to use in high-performance settings (byte
> crunching), and a bit too hung up on being standards compliant.
>
> I resumed working on it around a week ago, and solved all these issues!
>
> (I still do my best to keep R7RS compliance, but Guile is my prime
> *real* target.)
>
> So what is it?
>
> === Structured access to bytevector contents ===
I really want something like this BTW :) I was thinking that we can do
this on a proper low level, applying type tags to bytevectors. I want
something like http://luajit.org/ext_ffi.html for Guile, and data access
is part of it.
Andy
next prev parent reply other threads:[~2016-06-20 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 16:32 Bytestructures: a "type system" for bytevectors Taylan Ulrich Bayırlı/Kammer
2015-08-31 13:50 ` Taylan Ulrich Bayırlı/Kammer
2015-09-07 22:57 ` neil
2015-09-08 7:59 ` Taylan Ulrich Bayırlı/Kammer
2016-06-20 13:24 ` Andy Wingo [this message]
2016-06-20 22:05 ` Taylan Ulrich Bayırlı/Kammer
2016-06-20 23:47 ` Matt Wette
2016-06-21 7:50 ` Taylan Ulrich Bayırlı/Kammer
2016-06-21 12:53 ` Matt Wette
2016-06-24 14:33 ` Matt Wette
2016-06-24 14:47 ` Matt Wette
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y460gfhd.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=taylanbayirli@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).