or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
DevMeeting at RubyKaigi 2024
Near by RubyKaigi venue (not a RubyKaigi venue).
Japanese page: https://www.sakura.ad.jp/innobase/
Proposal from Matz
^(expr)
)?[Bug #20468] Segfault on safe navigation in
for
target (nobu)Preliminary discussion:
for foo&.bar in []; end
causes segfault.Discussion:
for
loopsfor a.b.c in [1, 2]; end
should evaluatea.b
twice?Conclusion:
[Feature #19979] Allow methods to declare that they don't accept a block via
&nil
(ufuk)method(:foo).parameters #=> [:noblock]
or maybe?Discussion:
yield
until called (unless tracked in parser maybe).eval
cases, so I am in favour of static annotation. Also zsuper… do we need to detect.&nil
syntax, but I find it is quite hard to tell at runtime.Conclusion:
[Feature #15554] warn/error passing a block to a method which never use a block (ko1)
rails/rails
test suite, relaxed brings it down to 10% false positive, and almost no false negative.&b
to duck typing methods seems helpful for readability and indicate "intentionally ignores block". But too much warnings is bad, maybe opt-in via flag/env var/pragma?--strict-unused-block-warning
/--pedantic-warnings
?)pedantic
category that gives more warnings?Conclusion:
[Feature #20470] Extract Ruby's Garbage Collector (peterzhu2118)
gc.c
andgc_impl.c
.gc.c
only contains code not specific to Ruby GC.gc_impl.c
contains the implementation of Ruby's GC.gc_impl.c
only uses public APIs in Ruby and a limited set of functions exposed ingc.c
. This allows us to buildgc_impl.c
independently of Ruby and plug Ruby's GC into itself.Discussion:
Conclusion:
[Misc #20434] Deprecate encoding-related regular expression modifiers p(kddnewton)
Discussion:
Conclusion:
[Feature #20415] Precompute literal String hash code during compilation (byroot / etienne) (byroot)
Discussion:
liquid-c
andrack
benchmarks.Conclusion:
[Feature #6648] Provide a standard API for retrieving all command-line flags passed to Ruby (eregon)
Discussion:
Process
instead ofRbConfig
, but it is not that important.RbConfig
already has.ruby
method to return running Ruby path, so it makes sense to add.ruby_args
method as well.Conclusion:
[Misc #20406] Question about Regexp encoding negotiation (andrykonchin)
Regexp#encoding
method returns) is calculated in case an encoding modifier (e.g.u
,e
, etc) is specified.US-ASCII
characters hasUS-ASCII
encoding, otherwise a regular expression is assumed to use the source encoding. This can be overridden with encoding modifiers./#{} a/e
- it's supposed to haveEUC-JP
encoding but actually hasUS-ASCII
.Discussion:
Conclusion:
[Misc #20407] Question about applying encoding modifier to an interpolated Regexp (andrykonchin)
u
,e
, etc) is specified to a Regexp with interpolation (e.g./a #{ "b".encode("windows-1251") } c/e
).Discussion:
Conclusion:
[Bug #20421] String#index and String#byteindex don't clear
$~
when offset > size (or bytesize) (andrykonchin)String#{index,rindex,byteindex,byterindex}
methods when called with Regexp argument andoffset
out of scope should clear the$~
global variable.String#index
andString#byteindex
don't clear$~
whenoffset
> size, only whenoffset
<-size
.Conclusion:
[Bug #20416] IO#read doesn't preserve buffer encoding if
maxlen = nil
(andrykonchin)IO#read
and similar methods when called with buffer argument preserve its encoding.IO#read
doesn't do so in case themaxlen
argument isnil
.Discussion:
Conclusion:
[Bug #20319] Singleton class is being frozen lazily in some cases (andrykonchin)
#freeze
method call) only its own singleton class becomes frozen immediately.#singleton_class
method call.Discussion:
Conclusion:
[Feature #20425] Optimize forwarding callers and callees (tenderlovemaking)
...
callers and calleesdef foo(...)
depends on the caller (foo(1,2)
has different stack size thanfoo(1)
)Discussion:
Conclusion:
[Feature #20443] Allow Major GC's to be disabled (eightbitraptor)
GC#disable_major
,GC#enable_major
,GC#need_major?
,GC#disable_major_gc
etc.GC#disable(type: major)
respond_to?
, and are able to be undefined.Discussion:
GC
methods to be implemented in the implementation, so alternative implementations can define them different. Already some methods do not make sense for alternative GC implementations.Conclusion:
[Bug #20455] rb_errinfo() inconsistent with $! in the caller Ruby code (eregon)
Discussion:
rescue
/ensure
on stack):rb_errinfo()
, what for?Conclusion:
[Feature #20437] Could be the licensing conditions be made less ambiguous?
[Bug #20438][Bug #20439] String format "%\n" and "%\0" does not raise format error
"%\n"
has been treated as"%%"
since commit:554b989ba162 , probably Tue Aug 6 01:12:32 1996 according to the commit log.[Feature #20460] Ripper eval option
[Misc #20432] Proposal for workflow changes related to teeny releases (ufuk)
Discussion:
Ufuk: People may see Ruby as an healthier project if they get more releases
Benoit: How about making x.y.1 release faster with most important fixes, even if that means not backporting every fix?
Having too many releases may degrade user experience if they need to upgrade more often or if they need to go through many releases to get a bugfix
A more established process may make it easier for feature implementers to submit fixes for teeny versions
Some users are concerned by the lack of communication on the status of upcomming releases. A more established process would make it easier for user to know when to expect bug fixes
Jean: recent releases had bugs preventing people to upgrade while at the same time being eager to update to benefit from performance improvements
Conclusion:
Extra Agenda Items
kddnewton
[Misc #20238] Use prism for mk_builtin_loader.rb
mk_builtin_loader
more elegant and complete approach. Can we merge this?mk_builtin_loader
Conclusion:
[Bug #20401] Duplicated when clause warning line number
Conclusion:
tenderlovemaking
[Bug #20424] ZLib::GZipReader always double allocates strings when passed outbuf, significantly increasing memory usage
Discussion:
Conclusion:
eregon
[Feature #20331] Should parser warn hash duplication and when clause?
Discussion: