| Age | Commit message (Collapse) | Author |
|---|
|
|
|
- `OpenSSL` here is not the class.
- libexecinfo on FreeBSD is present in the base system of all
supported releases, since 2017.
|
|
Get rid of using ambiguous demonstratives as link anchors, for the
accessibility's sake.
|
|
|
|
|
|
This reverts commit 974ed1408c516d1e8f992f0b304e2de6f8bd5c1f.
|
|
This reverts commit 1fa93fb9488a32018101689fd727965fd5874eb5.
|
|
|
|
(https://github.com/ruby/strscan/pull/96)
#peek_byte and #scan_byte not updated (not available in my repo --
sorry).
---------
https://github.com/ruby/strscan/commit/0123da7352
Co-authored-by: Sutou Kouhei <[email protected]>
|
|
The example code in the documentation for the `String#encode` method has
a typo in the `fallback` option. The example code uses `h` as the
fallback option, but it should use `hash` instead to match the variable
name in the example code.
|
|
Guard clauses can only be used in `case` pattern matching statements,
not in `=>`/`in` operators.
|
|
Clang 18 has the bugfix we need, so we no longer need to tell people to
compile Clang from source.
|
|
Noticed this small type while reading the docs.
|
|
|
|
|
|
https://blade.ruby-lang.org/ruby-dev/39325
|
|
- Fix markups as RDoc.
- Remove already descriptions of removed methods.
|
|
* YJIT: update code optimization tips in yjit.md
* Function => method
|
|
The directive is a lowercase `u` instead of an uppercase `U`. Adjusted
input and output to match.
Reported by Leah Neukirchen.
|
|
|
|
We use the following site for that now:
* https://tools.ietf.org/ or http
* https://datatracker.ietf.org or http
Today, IETF said the official site of RFC is www.rfc-editor.org.
FYI: https://authors.ietf.org/en/references-in-rfcxml
I replaced them to www.rfc-editor.org.
|
|
Signed-off-by: crazeteam <[email protected]>
|
|
(https://github.com/ruby/irb/pull/901)
* Always save irb_history in HOME or XDG_CONFIG_HOME
Also split irbrc search logic from irb_history search logic as a refactor
* Remove IRB.conf[:RC_NAME_GENERATOR] because it's not configurable
This conf is used to specify which irbrc to load. Need to configure before irbrc is loaded, so it's actually not configurable.
This conf is also used for history file search, but it is configurable by conf[:HISTORY_FILE].
* remove rc_file_test because it is tested with rc_files, remove useless test setup
* Make internal irbrc searching method private
https://github.com/ruby/irb/commit/11d03a6ff7
|
|
There is a weird gotcha I already forgot twice.... and regret not to have found in doc.
See https://dev.to/okuramasafumi/be-sure-ensure-doesn-t-return-value-implicitly-8gp
|
|
* YJIT: Let yjit_perf.py support perf with Python disabled
* Update yjit.md about perf
* Recommend the extra interface by default
|
|
Since https://github.com/ruby/ruby/commit/fbb4e3f96c10de2240f2d87eac19cf6f62f65fea
`YAML` does not unmarshal arbitrary ruby objects.
|
|
Searching the file in the "current directory" could be read as the
directory from which RDoc is run. This is incorrect, as the file is
first searched in the directory containing the current documented file.
Also this directory is searched before the `--include` directories.
https://github.com/ruby/rdoc/commit/aa2d98ee5e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
s/copmiler-rt/compiler-rt/
|
|
|
|
I don't really think ASAN works well at all on any version of Ruby from
before https://bugs.ruby-lang.org/issues/20001 was landed. Update the
docs to clarify what works, and what does not work.
Also there's no need to compile at `-O0`; this was probably just hiding
some of the problems with our stack scanning that were fixed in the
above issue.
[Bug #20248]
|
|
* YJIT: Allow tracing a counted exit
* Avoid clobbering caller-saved registers
|
|
"builtin-baseline": "53bef8994c541b6561884a8395ea35715ece75db" is 2024.01.12
released version of vcpkg.
https://github.com/microsoft/vcpkg/releases/tag/2024.01.12
|
|
|
|
YJIT: reduce default exec mem size to 48MiB based
Based on user feedback from @jhawthorn and others.
Better for small and memory-constrained deployments.
NOTE: This commit should be included in the next Ruby 3.3.x point
release. @xrxr should we tag someone specific?
|
|
I'm not aware of this information being available
anywhere else.
|
|
|
|
|
|
|
|
|
