Marc-André Bélanger comments

Results 58 comments of


                                            Marc-André Bélanger

Safer defaults for make-vector, make-string, make-u8vector, and so on

@AlexKnauth can you provide an example of the current behaviour? From what I see, only the return value is unspecified in some cases (`subvector-fill!`, `substring-fill!`). ``` > (make-vector 10) #(0...

Safer defaults for make-vector, make-string, make-u8vector, and so on

Ah! That's a bug to be filed in Gambit then! So somehow your returned vector contains garbage? If so, then vyzo's solution wouldn't change a thing. Do you have any...

Safer defaults for make-vector, make-string, make-u8vector, and so on

That is concerning. Does it happen with small or large vectors? Which kind of vector?

Safer defaults for make-vector, make-string, make-u8vector, and so on

Ok, if you are using `(declare (not safe))`, then an undefined `fill` argument is probably the culprit. `##make-u8vector` won't initialize, but `make-u8vector` will, and I was worried the bug was...

Safer defaults for make-vector, make-string, make-u8vector, and so on

@AlexKnauth see https://github.com/gambit/gambit/commit/fc132b2f9d03b4f0bde9c70cc406ddcc9fbbcbe9

Quasistring.

Docs coming in another commit.

Quasistring.

Here is one issue that needs to be adressed. The following does not fully work: ```scheme > (import :std/misc/text) > (def t (template/hash "(2 + #{n}) is #{(+ 2 n)}"))...

Quasistring.

We will not be merging templates as their implementation is not considered ready yet.

Quasistring.

Hi @fare, Two things: First, I am not at all surprised that it is suboptimal as this is the first ever parser I wrote. I just brute-forced my way out....

Quasistring.

Thanks @fare, I understand better your position. What you are proposing is semantically different from what I have here. We _could_ make a distinction between function calls and variables in...