[#103135] [Ruby master Feature#17768] Proposal: Downward assignments — mame@...

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

10 messages 2021/04/01

[#103162] [Ruby master Feature#17773] Alias `Numeric#zero?` and `Float#zero?` as `Numeric#empty?` and `Float#empty?` — sawadatsuyoshi@...

Issue #17773 has been reported by sawa (Tsuyoshi Sawada).

9 messages 2021/04/02

[#103241] [Ruby master Bug#17777] 2.6.7 fails to build on macOS: implicit declaration of function 'rb_native_mutex_destroy' is invalid in C99 — eregontp@...

Issue #17777 has been reported by Eregon (Benoit Daloze).

17 messages 2021/04/05

[#103280] [Ruby master Bug#17781] Resolv::DNS RequestID table allocations are never freed, causing DNS lookups to eventually hang — supermathie@...

SXNzdWUgIzE3NzgxIGhhcyBiZWVuIHJlcG9ydGVkIGJ5IHN1cGVybWF0aGllIChNaWNoYWVsIEJy

9 messages 2021/04/07

[#103305] [Ruby master Feature#17785] Allow named parameters to be keywords — marcandre-ruby-core@...

Issue #17785 has been reported by marcandre (Marc-Andre Lafortune).

21 messages 2021/04/08

[#103310] [Ruby master Feature#17786] Proposal: new "ends" keyword — jzakiya@...

Issue #17786 has been reported by jzakiya (Jabari Zakiya).

13 messages 2021/04/08

[#103317] [Ruby master Bug#17787] Four AIX build issues with xlc compiler and ruby-3.0.1 — lamont@...

Issue #17787 has been reported by lamont (Lamont Granquist).

9 messages 2021/04/08

[#103342] [Ruby master Feature#17790] Have a way to clear a String without resetting its capacity — jean.boussier@...

Issue #17790 has been reported by byroot (Jean Boussier).

14 messages 2021/04/09

[#103386] [Ruby master Bug#17793] `shorten-64-to-32` error for 32-bit Android due to `struct stat` definition — xtkoba+ruby@...

Issue #17793 has been reported by xtkoba (Tee KOBAYASHI).

8 messages 2021/04/11

[#103400] [Ruby master Feature#17795] `before_fork` and `after_fork` callback API — jean.boussier@...

Issue #17795 has been reported by byroot (Jean Boussier).

42 messages 2021/04/12

[#103434] [Ruby master Bug#17799] Seg fault in rb_class_clear_method_cache — stanhu@...

Issue #17799 has been reported by stanhu (Stan Hu).

14 messages 2021/04/13

[#103481] [Ruby master Feature#17808] Feature Request: JS like splat of Object properties as named method parameters — brad.krane@...

Issue #17808 has been reported by Lithium (Brad Krane).

8 messages 2021/04/16

[#103556] [Ruby master Bug#17820] `Errno::EINVAL` from `Process.kill` with available signal on Windows — alex.wayfer@...

SXNzdWUgIzE3ODIwIGhhcyBiZWVuIHJlcG9ydGVkIGJ5IEFsZXhXYXlmZXIgKEFsZXhhbmRlciBQ

9 messages 2021/04/22

[#103591] [Ruby master Bug#17827] Monitor is not fiber safe — samuel@...

Issue #17827 has been reported by ioquatix (Samuel Williams).

11 messages 2021/04/25

[#103593] [Ruby master Misc#17828] Deprecate use of master and slave — yyoshida.at.work@...

Issue #17828 has been reported by yyoshida.at.work@gmail.com (Yasuhiro Yoshida).

10 messages 2021/04/26

[#103596] [Ruby master Feature#17830] Add Integer#previous and Integer#prev — rafasoaresms@...

Issue #17830 has been reported by rafasoares (Rafael Soares).

9 messages 2021/04/26

[#103631] [Ruby master Feature#17837] Add support for Regexp timeouts — sam.saffron@...

Issue #17837 has been reported by sam.saffron (Sam Saffron).

45 messages 2021/04/27

[ruby-core:103266] [Ruby master Feature#12133] Ability to exclude start when defining a range

From: arima.yasuhiro@...
Date: 2021-04-07 06:49:26 UTC
List: ruby-core #103266
Issue #12133 has been updated by arimay (yasuhiro arima).



Definition of a range object that exclude a start position, and its shorthand notation.

Since we have #exclude_end? we also want #exclude_begin? .

    class Range
      def initialize(begin, end, exclude_end=false, exclude_begin=false)
      def exclude_begin?

Shorthand, by known as the neko operator.

    notation        meaning         new
    b..e            b <= v <= e     Range.new(b, e)
    b..^e           b <= v <  e     Range.new(b, e, true) # the same as "b...e"
    b^..e           b <  v <= e     Range.new(b, e, false, true)
    b^..^e          b <  v <  e     Range.new(b, e, true,  true)

    with nil.

    ..e                  v <= e     Range.new(nil, e)
    ^..e                 v <= e     Range.new(nil, e)
    ..^e                 v <  e     Range.new(nil, e, true)
    ^..^e                v <  e     Range.new(nil, e, true)
    b..             b <= v          Range.new(b, nil, false, false)
    b..^            b <= v          Range.new(b, nil, false, false)
    b^..            b <  v          Range.new(b, nil, false, true)
    b^..^           b <  v          Range.new(b, nil, false, true)

The priority of the range operators is the same.

    < Higher >
    ||
    ..  ...  ..^  ^..  ^..^
    ?:
    < Lower >

Situation: Notation.

    range  =  0^..100     # 0    < v <=  100
    range  =  100^..1000  # 100  < v <= 1000
    range  =  1000^..     # 1000 < v

Situation: Pass to argument for method call.

    [ 0^..100,  100^..1000,  1000^.. ].each do |range|
      pp  Items.where( price: range ).all
    end

Situation: Build expression.(e.g. query script)

    def build( v, range )
      b  =  range.begin
      e  =  range.end
      exprs  =  []
      if range.exclude_begin?
        exprs  <<  "#{b} < #{v}"
      elsif b
        exprs  <<  "#{b} <= #{v}"
      end
      if range.exclude_end?
        exprs  <<  "#{v} < #{e}"
      elsif e
        exprs  <<  "#{v} <= #{e}"
      end
      exprs.join(" and ")
    end

The new feature will enables more clear code.
We believe this feature will be very useful for developers.



----------------------------------------
Feature #12133: Ability to exclude start when defining a range
https://bugs.ruby-lang.org/issues/12133#change-91351

* Author: slash_nick (Ryan Hosford)
* Status: Feedback
* Priority: Normal
----------------------------------------
An intuitive, approach would be to allow defining ranges like so:

~~~
[1..10]
[1..10)
(1..10]
(1..10)
~~~

... where a square bracket indicates boundary inclusion and a parenthesis represents boundary exclusion. The syntax there is obviously not going to work, but it demonstrates the idea.

A more feasible, still intuitive, solution might look like the following

~~~
(1..10)                # [1..10]
(1...10)               # [1..10) ... Alternatively: (1..10).exclude_end
(1..10).exclude_start  # (1..10]
(1...10).exclude_start # (1..10) ... Alternatively: (1..10).exclude_start.exclude_end
~~~

For consistency, I think we'd also want to add `#exclude_start?` & `#exclude_end` methods.



-- 
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>

In This Thread

Prev Next