[#107430] [Ruby master Feature#18566] Merge `io-wait` gem into core IO — "byroot (Jean Boussier)" <noreply@...>
Issue #18566 has been reported by byroot (Jean Boussier).
22 messages
2022/02/02
[ruby-core:107419] [Ruby master Feature#18563] Add "graphemes" and "each_grapheme aliases
From:
"mame (Yusuke Endoh)" <noreply@...>
Date:
2022-02-01 20:27:58 UTC
List:
ruby-core #107419
Issue #18563 has been updated by mame (Yusuke Endoh). Description updated (I have added to the description an url to matz's original statement) ---------------------------------------- Feature #18563: Add "graphemes" and "each_grapheme aliases https://bugs.ruby-lang.org/issues/18563#change-96319 * Author: shan (Shannon Skipper) * Status: Open * Priority: Normal ---------------------------------------- https://bugs.ruby-lang.org/issues/13780#note-10 > grapheme sounds like an element in the grapheme cluster. How about each_grapheme_cluster? > If everyone gets used to the grapheme as an alias of grapheme cluster, we'd love to add an alias each_grapheme. > Matz. Languages that have added grapheme cluster support seem to be almost exclusively opting for the shorter "graphemes" alias as a part that stands for the whole. * JavaScript/TypeScript grapheme-splitter library: `splitGraphemes` * PHP: `grapheme_extract` * Zig ziglyph library: `GraphemeIterator` * Golang uniseg library: `NewGraphemes` * Matlab: `splitGraphemes` * Python grapheme library: `graphemes` * Elixir: `graphemes` * Crystal uni_text_seg library: `graphemes` * Nim nim-graphemes library: `graphemes` * Rust unicode-segmentation library: `graphemes` Now that some time has passed and the "graphemes" alias for "grapheme clusters" has been fairly widely adopted by languages and libraries, I'd like to go ahead and propose a `graphemes` alias for `grapheme_clusters` and an `each_grapheme` alias for `each_grapheme_cluster`. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>