[#118180] [Ruby master Bug#20525] Percent string literal with indentation support — "bradgessler (Brad Gessler) via ruby-core" <ruby-core@...>

Issue #20525 has been reported by bradgessler (Brad Gessler).

8 messages 2024/06/04

[#118243] [Ruby master Feature#20564] Switch default parser to Prism — "kddnewton (Kevin Newton) via ruby-core" <ruby-core@...>

Issue #20564 has been reported by kddnewton (Kevin Newton).

11 messages 2024/06/07

[#118269] [Ruby master Bug#20570] Nokey behavior changed since 3.3. — "ksss (Yuki Kurihara) via ruby-core" <ruby-core@...>

Issue #20570 has been reported by ksss (Yuki Kurihara).

8 messages 2024/06/10

[#118279] [Ruby master Bug#20573] Warning.warn shouldn't be called for disabled warnings — "tenderlovemaking (Aaron Patterson) via ruby-core" <ruby-core@...>

Issue #20573 has been reported by tenderlovemaking (Aaron Patterson).

10 messages 2024/06/10

[#118281] [Ruby master Misc#20574] DevMeeting-2024-07-11 — "mame (Yusuke Endoh) via ruby-core" <ruby-core@...>

Issue #20574 has been reported by mame (Yusuke Endoh).

12 messages 2024/06/11

[#118346] [Ruby master Bug#20586] Some filesystem calls in dir.c are missing error handling and can return incorrect results if interrupted — "ivoanjo (Ivo Anjo) via ruby-core" <ruby-core@...>

Issue #20586 has been reported by ivoanjo (Ivo Anjo).

13 messages 2024/06/19

[#118347] [Ruby master Bug#20587] dir.c calls blocking system calls while holding the GVL — "ivoanjo (Ivo Anjo) via ruby-core" <ruby-core@...>

Issue #20587 has been reported by ivoanjo (Ivo Anjo).

7 messages 2024/06/19

[#118360] [Ruby master Bug#20588] RangeError: integer 132186463059104 too big to convert to 'int' since cdf33ed5f37f9649c482c3ba1d245f0d80ac01ce with YJIT enabled — "yahonda (Yasuo Honda) via ruby-core" <ruby-core@...>

Issue #20588 has been reported by yahonda (Yasuo Honda).

10 messages 2024/06/20

[#118388] [Ruby master Feature#20594] A new String method to append bytes while preserving encoding — "byroot (Jean Boussier) via ruby-core" <ruby-core@...>

SXNzdWUgIzIwNTk0IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGJ5cm9vdCAoSmVhbiBCb3Vzc2llciku

32 messages 2024/06/25

[ruby-core:118214] [Ruby master Misc#20488] Document source file size restrictions

From: "kddnewton (Kevin Newton) via ruby-core" <ruby-core@...>
Date: 2024-06-06 14:16:42 UTC
List: ruby-core #118214
Issue #20488 has been updated by kddnewton (Kevin Newton).

Status changed from Open to Closed

Thank you!

----------------------------------------
Misc #20488: Document source file size restrictions
https://bugs.ruby-lang.org/issues/20488#change-108703

* Author: kddnewton (Kevin Newton)
* Status: Closed
----------------------------------------
I was hoping we might be able to decide on an official maximum size for a s=
ource file in terms of bytes/lines/columns/etc.

Ruby uses fixed integer sizes to represent line numbers, column numbers, of=
fsets, etc. These can overflow with files that are too big. Sometimes they =
will fail with cryptic messages like:

```
ruby: negative string size (or size too big) (ArgumentError)
```

(That's for 2^31 "a"s in a row.) Note that for python for the same file you=
 will get:

```
OverflowError: Parser column offset overflow - source line is too big
```

and for perl you will get:

```
Identifier too long at test.pl line 1.
```

For files with 2^32 newlines, Ruby just crashes on my machine with the curr=
ent parser (prism finishes, but its newline counter overflows so it gets al=
l the offsets wrong).

Would it be okay to say:

* maximum line: 31 bits
* maximum column: 32 bits
* maximum file byte size: 32 bits

This would also help with memory savings =E2=80=94 I would like to only use=
 32 bits for offsets in the file, as opposed to the current 64 bits I'm usi=
ng (which seems unnecessarily large).



--=20
https://bugs.ruby-lang.org/

In This Thread

Prev Next