[#86520] [Ruby trunk Bug#14681] `syswrite': stream closed in another thread (IOError) — samuel@...
Issue #14681 has been reported by ioquatix (Samuel Williams).
3 messages
2018/04/12
[#86755] [Ruby trunk Feature#14723] [WIP] sleepy GC — normalperson@...
Issue #14723 has been reported by normalperson (Eric Wong).
6 messages
2018/04/29
[ruby-core:86668] [Ruby trunk Feature#14709] Proper pattern matching
From:
shevegen@...
Date:
2018-04-24 16:20:01 UTC
List:
ruby-core #86668
Issue #14709 has been updated by shevegen (Robert A. Heiler). I think only matz can answer that. On a side note, I am not aware of a issue request about it. Has this already been suggested, or is it only a presentation? If it has not yet been proposed formally through an issue request on the tracker here, then perhaps that should be done. ---------------------------------------- Feature #14709: Proper pattern matching https://bugs.ruby-lang.org/issues/14709#change-71626 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- On RubyKaigi 2017, there was a [presentation](http://rubykaigi.org/2017/presentations/yotii23.html) of Yuki Torii about possible implementation of pattern matching. The syntax proposed in presentation was: ```ruby res = [:ng, 500] case res when %p([:ng, status]) p status end ``` The proposed syntax seem to feel pretty consistent, and the implementation (forked Ruby interpreter) was working at this moment. As @ko1 was one of the contributors to the experiment, I don't suppose Ruby core team is not aware of the proposal, so I'd like to know what the status of it? Are there some plans for full-strength pattern matching in Ruby 3 (with proposed, or any other, syntax)? PS: There are many existing gems with some kind "almost real" pattern matching (including recently emerged [Qo](https://github.com/baweaver/qo)), yet I believe that the _only_ useful pattern matching can be provided language core. Otherwise, two main goals can't be achieved: * reasonable performance (as the pattern-matching is useful mostly in complicated algorithms, which tend to repeat matches thousands of times); * unpacking of parts of the patterns into local variables. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>