ruby-next 0.5.3 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6a7b8fa605da45a73b34dfcd1f1b52bf3ebbd94ab5e4b63a6d10a5a2f8e23d32
-  data.tar.gz: 53ab54363dad82f1795b673d8b009b4d9d6848f7101d4e58032fef026b063ce7
+  metadata.gz: 7b1c1af8cbe6211f553a3111863bf727e7438220174dc3d5b1126fdd46c5c5ba
+  data.tar.gz: 66fe1d334298706ec37cc73af042b83f6e770f8888b8a2a9227b1950d139df23
 SHA512:
-  metadata.gz: b6225ef7d9c420cfb1582f3946a0db5a32ccb4b0a8d24862f7229f8359f5d1eed717a5132dd162d25c67b1c07fddc00bf1699878f1293cc3bc0c91d66003da01
-  data.tar.gz: 3ebb50211128989c163006b053789daa85553fe1a47ddce846a39527a07cdb9b5530faddb2e0be6f35a8197068b4dc1cb5dd2105b6f2c02dd3ebdcf6c162bfbc
+  metadata.gz: 8a24a83d3f705da786d64878bf87c9375685508e6eb9c69b84144d02d005733fc92ff58adafa89d49721b75983ff4b8d1c8f193cd02868b613f6dc829e04907c
+  data.tar.gz: 0c5aa1e100aec167c965c13330fc4fa71ac0210233ee800ed09ddf0cf0256b97aa52ab6cfc0d210e5aa8d19bb2220d21766f90761edb3be271efbda922adae39

data/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 ## master
 
+## 0.6.0 (2020-04-23)
+
+- Changed the way edge/proposed features are activated. ([@palkan][])
+
+Use `--edge` or `--proposed` flags for `ruby-next nextify` or
+`require "ruby-next/language/{edge,proposed}"` in your code.
+
+See more in the [Readme](./README.md#proposed-and-edge-features).
+
+- Updated RuboCop integration. ([@palkan][])
+
+Make sure you use `TargetRubyVersion: next` in your RuboCop configuration.
+
+- Upgraded to `ruby-next-parser` for edge features. ([@palkan][])
+
+It's no longer needed to use Parser gem from Ruby Next package registry.
+
 ## 0.5.3 (2020-03-25)
 
 - Enhance logging. ([@palkan][])

data/README.md

@@ -27,6 +27,7 @@ That's why Ruby Next implements the `master` features as fast as possible.
 ## Table of contents
 
 - [Overview](#overview)
+- [Quick Start](#quick-start)
 - [Polyfills](#using-only-polyfills)
 - [Transpiling](#transpiling)
   - [Modes](#transpiler-modes)
@@ -51,6 +52,27 @@ programmatically or via CLI. It also could be done in runtime.
 Currently, Ruby Next supports Ruby versions 2.5+ (including JRuby 9.2.8+).
 Please, [open an issue](https://github.com/ruby-next/ruby-next/issues/new/choose) if you would like us to support older Ruby versions.
 
+## Quick start
+
+The quickest way to start experimenting with Ruby Next is to install the gem and run a sample script. For example:
+
+```sh
+# Install Ruby Next globally
+$ gem install ruby-next
+
+# Call ruby with -ruby-next flag
+$ ruby -ruby-next -e "
+ case {hello: 'martian'}
+ in hello: hello if hello =~ /human/
+   puts '🙂'
+ in hello: 'martian'
+   puts '👽'
+ end
+"
+
+=> 👽
+```
+
 ## Using only polyfills
 
 First, install a gem:
@@ -79,7 +101,7 @@ using RubyNext
 
 Ruby Next only refines core classes if necessary; thus, this line wouldn't have any effect in the edge Ruby.
 
-**NOTE:** Even if the runtime already contains a monkey-patch with the backported functionality, we consider the method as _dirty_ and activate the refinement for it. Thus, you always have a predictable behaviour. That's why we recommend using refinements for gems development.
+**NOTE:** Even if the runtime already contains a monkey-patch with the backported functionality, we consider the method as _dirty_ and activate the refinement for it. Thus, you always have predictable behaviour. That's why we recommend using refinements for gems development.
 
 Alternatively, you can go with monkey-patches. Just add this line:
 
@@ -124,7 +146,7 @@ gem install ruby-next
 
 Ruby Next currently provides two different modes of generating transpiled code: _AST_ and _rewrite_.
 
-In the AST mode, we parse the source code into AST, modifies this AST and **generate a new code from AST** (using [unparser][unparser]). Thus, the transpiled code being identical in terms of functionality has a different formatting.
+In the AST mode, we parse the source code into AST, modifies this AST and **generate a new code from AST** (using [unparser][unparser]). Thus, the transpiled code being identical in terms of functionality has different formatting.
 
 In the rewrite mode, we apply changes to the source code itself, thus, keeping the original formatting of the unaffected code (in a similar way to RuboCop's autocorrect feature).
 
@@ -292,10 +314,12 @@ To enable this integration, add the following line after the `require "bootsnap/
 require "ruby-next/language/bootsnap"
 ```
 
-**NOTE:** there is no way to invalidate the cache when you upgrade Ruby Next (e.g., due to the bug fixes), so you should do this manually.
+**NOTE:** There is no way to invalidate the cache when you upgrade Ruby Next (e.g., due to the bug fixes), so you should do this manually.
 
 ## `uby-next`
 
+_This is [not a typo](https://github.com/ruby-next/ruby-next/pull/8), that’s the way `ruby -ruby-next` works: it’s equal to `ruby -r uby-next`, and [`uby-next.rb`](https://github.com/ruby-next/ruby-next/blob/master/lib/uby-next.rb) is a special file that activates the runtime mode._
+
 You can also enable runtime mode by requiring `uby-next` while running a Ruby executable:
 
 ```sh
@@ -328,7 +352,7 @@ require:
   - ruby-next/rubocop
 ```
 
-**NOTE:** You should use `TargetRubyVersion: 2.7`.
+You must set `TargetRubyVersion: next` to make RuboCop use a Ruby Next parser.
 
 Alternatively, you can load the patch from the command line by running: `rubocop -r ruby-next/rubocop ...`.
 
@@ -349,48 +373,33 @@ This includes:
 - Features proposed in [Ruby bug tracker](https://bugs.ruby-lang.org/) (_proposed_)
 - Features once merged to master but got reverted.
 
-These features require a [custom parser](#using-ruby-next-parser).
+These features are disabled by default, you must opt-in in one of the following ways:
 
-Currently, the only such feature is the [_method reference_ operator](https://bugs.ruby-lang.org/issues/13581):
+- Add `--edge` or `--proposed` option to `nextify` command when using CLI.
+- Enable programmatically when using a runtime mode:
 
-- Add `--enable-method-reference` option to `nextify` command when using CLI.
-- OR add it programmatically when using a runtime mode (see [example](https://github.com/ruby-next/ruby-next/blob/master/default.mspec)).
-- OR set `RUBY_NEXT_ENABLE_METHOD_REFERENCE=1` environment variable (works with CLI as well).
-
-### Prerequisites
-
-Our own version of [parser][next_parser] gem is hosted on Github Package Registry. That makes the installation process a bit more complicated than usual.
-
-You must obtain an access token to use it. See the [GPR docs](https://help.github.com/en/github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry#authenticating-to-github-package-registry).
-
-### Installing with Bundler
+```ruby
+# It's important to load language module first
+require "ruby-next/language"
 
-First, configure your bundler to access GPR:
+require "ruby-next/language/edge"
+# or
+require "ruby-next/language/proposed"
 
-```sh
-bundle config --local https://rubygems.pkg.github.com/ruby-next USERNAME:ACCESS_TOKEN
+# and then activate the runtime mode
+require "ruby-next/language/runtime"
+# or require "ruby-next/language/bootsnap"
 ```
 
-Then, add to your Gemfile:
-
-```ruby
-source "https://rubygems.pkg.github.com/ruby-next" do
-  gem "parser", "~> 2.7.0.100", "< 2.7.1"
-end
-
-gem "ruby-next"
-```
+- Set `RUBY_NEXT_EDGE=1` or `RUBY_NEXT_PROPOSED=1` environment variable.
 
-**NOTE:** we don't add `parser` and `unparser` to the gem's runtime deps, 'cause they're not necessary if you only need polyfills.
+### Supported edge features
 
-### Installing globally via `gem`
+Not yet.
 
-You can install `ruby-next` globally by running the following commands:
+### Supported proposed features
 
-```sh
-gem install parser -v "~> 2.7.0.100" -v "< 2.7.1" --source "https://USERNAME:ACCESS_TOKEN@rubygems.pkg.github.com/ruby-next"
-gem install ruby-next
-```
+- _Method reference_ operator (`.:`) ([link](https://bugs.ruby-lang.org/issues/13581)).
 
 ## Contributing
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby-next
 version: !ruby/object:Gem::Version
-  version: 0.5.3
+  version: 0.6.0
 platform: ruby
 authors:
 - Vladimir Dementyev
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-03-25 00:00:00.000000000 Z
+date: 2020-04-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ruby-next-core
@@ -25,19 +25,19 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: parser
+  name: ruby-next-parser
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 2.7.0.5
+        version: 2.8.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 2.7.0.5
+        version: 2.8.0.0
 - !ruby/object:Gem::Dependency
   name: unparser
   requirement: !ruby/object:Gem::Requirement