flexi-streams icon indicating copy to clipboard operation
flexi-streams copied to clipboard

Flexible bivalent streams for Common Lisp

Results 11 flexi-streams issues
Sort by recently updated
recently updated
newest added

Replace `keywords` in `defpackage` `:export` and `:shadow` clauses with uninterned symbols. This avoids interning them in `*package*`, which should simplify autocompletion and may improve garbage collection.

Hi guys, I am trying to run JSON parser `(yason:parse)` with `flexi-streams:in-memory-stream` directly, because `(yason:parse)` can accept string steam input directly. Then SBCL gives me the error when I did...

Running ```lisp (with-open-file (in "2-byte-file" :element-type '(unsigned-byte 8)) (setq in (make-flexi-stream in)) (setf (flexi-stream-position in) 1) (read-byte in)) ``` returns the first byte, while I would expect the second byte....

This is more of a feature request, I guess. `flexi-stream-position` is currently not supported for `vector-input-stream`, it would be consistent to have it.

When building decode.lisp with SBCL getting the error: ; file: /flexi-streams/decode.lisp ; in: ; DEFINE-CHAR-DECODERS (FLEXI-UTF-16-LE-FORMAT FLEXI-CR-UTF-16-LE-FORMAT FLEXI-CRLF-UTF-16-LE-FORMAT) ; (FLEXI-STREAMS::READ-NEXT-BYTE) ; --> PROG1 LET OR LET IF COND IF THE...

Java's standard library has routines that generate "modified" UTF-8 strings, which are unreadable using the standard UTF-8 support in FLEXI-STREAMS. The following link describes the differences, which are aimed at...

Hi folks, I'm working on a toy project that involves encoding/decoding some binary data, and I happened to notice that using flexi-streams' in-memory streams is much *much* slower vs. reading/writing...

The stream is created by `drakma:http-request` with `:force-binary t` We can seen in the inspect below that it is "wellformed" AFAIK, having ELEMENT-TYPE: FLEXI-STREAMS:OCTET. But when my code sends it...

Hey all, One feature I tend to miss often is the ability to have a stream output to a string with a fill-pointer ala `with-output-to-string`, but with indefinite extent so...

``` $ sbcl --version SBCL 2.4.4 $ sbcl --script