ruby-next 0.10.3 → 0.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 13bd3de07b288ceab89e02d629db39c0946fb93be30c84806d945f923b549ab2
-  data.tar.gz: 331bfca63292c880faadfe2d74ced0132320a55053305898e0a01025fb412f5c
+  metadata.gz: 2080439e0c5896a9024364465b3787c36c3a846196b274a7e72643c595523701
+  data.tar.gz: d74697e6e53f87343d38e7551568f62bfa1308f3ff756e090c295d14096511b5
 SHA512:
-  metadata.gz: 1abb1c61664fa3c52a7af52618de02dd47b99c644fa305a085b6c1302d7329ce7c9f7d43470679d9e644baf1e8e3062f871769e2e68e6fa22b6d396e40270411
-  data.tar.gz: 576682f808e5ab8eebc0ff1314b5a49dca222bdbe59190c9dcdac9883ad368a1cf16334d621986439954a37fc31dabac29737e03156bf65d9ace3973a2179ab1
+  metadata.gz: ef32fbe5c565e046a8913b6c71bab3021296c1002b5a314167392cd09b8d7d58085e71461b16e5cb3ef1935f6c9af926cc982793cce15ec2a2ca8dd3821f4fe4
+  data.tar.gz: 4004bcbd3f131ef74b28697b1c32dc253608a4c1b821568c0584acf51115cd2626ec3f97cfcb1269e7ead9093cee5fb600bd96f9d67112cf23757321801678ff

data/CHANGELOG.md

@@ -2,6 +2,50 @@
 
 ## master
 
+## 0.12.0 (2021-01-12)
+
+- Added required keyword arguments rewriter. ([@palkan][])
+
+Required kwargs were introduced in 2.1. Now we make them possible in 2.0.
+
+- Added numeric literals rewriter. ([@palkan][])
+
+Now it's possible to generate Ruby 2.0 compatible code from `2i + 1/3r`.
+
+- Fixed several safe navigation (`&.`) bugs. ([@palkan][])
+
+See [#68](https://github.com/ruby-next/ruby-next/issues/68) and [#69](https://github.com/ruby-next/ruby-next/issues/69).
+
+## 0.11.1 (2020-12-28)
+
+- Use separate _namespace_ for proposed features to avoid conflicts with new Ruby version. ([@palkan][])
+
+Previously, we used the upcoming Ruby version number for proposed features (e.g., `3.0.0`), which broke
+the load path setup, since transpiled files were not loaded anymore.
+Now that's fixed by using a _virtual_ version number for proposals (`1995.next.0`).
+
+## 0.11.0 (2020-12-24) 🎄
+
+- Extended proposed shorthand Hash syntax to support kwargs as well. ([@palkan][])
+
+You can try it: `x = 1; y = 2; foo(x:, y:) # => foo(x: x, y: y)`.
+
+- **Rewrite mode is used by default in transpiler**. ([@palkan][])
+
+- Move 3.0 features to stable features. ([@palkan][])
+
+- Refactor `a => x` and `a in x` to comply with Ruby 3.0. ([@palkan][])
+
+## 0.10.5 (2020-10-13)
+
+- Fix Unparser 0.5.0 compatibility. ([@palkan][])
+
+## 0.10.4 (2020-10-09)
+
+- Restrict Unparser dependency. ([@palkan][])
+
+Unparser 0.5.0 is currently not supported.
+
 ## 0.10.3 (2020-09-28)
 
 - Update RuboCop integration to handle the latest Parser changes. ([@palkan][])

data/README.md

@@ -35,6 +35,7 @@ Read more about the motivation behind the Ruby Next in this post: [Ruby Next: Ma
 ## Examples
 
 - Ruby gems
+  - [action_policy](https://github.com/palkan/action_policy)
   - [anyway_config](https://github.com/palkan/anyway_config)
   - [graphql-fragment_cache](https://github.com/DmitryTsepelev/graphql-ruby-fragment_cache)
 - Rails applications
@@ -92,8 +93,7 @@ def greet(val) =
       '👽'
     end
 
-greet(hello: 'martian') => greeting
-puts greeting
+puts greet(hello: 'martian')
 "
 
 => 👽
@@ -178,17 +178,17 @@ In the AST mode, we parse the source code into AST, modifies this AST and **gene
 
 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).
 
-By default, we use the AST mode. That could likely change in the future when we collect enough feedback on the rewrite mode and fix potential bugs.
-
 The main benefit of the rewrite mode is that it preserves the original code line numbers and layout, which is especially useful in debugging.
 
+By default, we use the rewrite mode. If you found a bug with rewrite mode which is not reproducible in the AST mode, please, let us know.
+
 You can change the transpiler mode:
 
 - From code by setting `RubyNext::Language.mode = :ast` or `RubyNext::Language.mode = :rewrite`.
-- Via environmental variable `RUBY_NEXT_TRANSPILE_MODE=rewrite`.
+- Via environmental variable `RUBY_NEXT_TRANSPILE_MODE=ast`.
 - Via CLI option ([see below](#cli)).
 
-**NOTE:** For the time being, Unparser [doesn't support](https://github.com/mbj/unparser/pull/142) new Ruby 2.7 AST nodes, so we always use rewrite mode in Ruby 2.7+.
+**NOTE:** For the time being, Unparser doesn't support Ruby 3.0 AST nodes, so we always use rewrite mode in Ruby 3.0+.
 
 ## CLI
 
@@ -219,7 +219,7 @@ Usage: ruby-next nextify DIRECTORY_OR_FILE [options]
 
 The behaviour depends on whether you transpile a single file or a directory:
 
-- When transpiling a directory, the `.rbnext` subfolder is created within the target folder with subfolders for each supported Ruby versions (e.g., `.rbnext/2.6`, `.rbnext/2.7`). If you want to create only a single version (the smallest), you can also pass `--single-version` flag. In that case, no version directory is created (i.e., transpiled files go into `.rbnext`).
+- When transpiling a directory, the `.rbnext` subfolder is created within the target folder with subfolders for each supported Ruby versions (e.g., `.rbnext/2.6`, `.rbnext/2.7`, `.rbnext/3.0`). If you want to create only a single version (the smallest), you can also pass `--single-version` flag. In that case, no version directory is created (i.e., transpiled files go into `.rbnext`).
 
 - When transpiling a file and providing the output path as a _file_ path, only a single version is created. For example:
 
@@ -322,7 +322,7 @@ due to the way feature resolving works in Ruby (scanning the `$LOAD_PATH` and ha
 
 If you're using [runtime mode](#runtime-usage) a long with `setup_gem_load_path` (e.g., in tests), the transpiled files are ignored (i.e., we do not modify `$LOAD_PATH`).
 
-\* Ruby Next avoids storing duplicates; instead, only the code for the earlier version is created and is assumed to be used with other versions. For example, if the transpiled code is the same for Ruby 2.5 and Ruby 2.6, only the `.rbnext/2.7/path/to/file.rb` is kept. That's why multiple entries are added to the `$LOAD_PATH` (`.rbnext/2.6` and `.rbnext/2.7` in the specified order for Ruby 2.5 and only `.rbnext/2.7` for Ruby 2.6).
+\* Ruby Next avoids storing duplicates; instead, only the code for the earlier version is created and is assumed to be used with other versions. For example, if the transpiled code is the same for Ruby 2.5 and Ruby 2.6, only the `.rbnext/2.7/path/to/file.rb` is kept. That's why multiple entries are added to the `$LOAD_PATH` (`.rbnext/2.6`, `.rbnext/2.7`, and `.rbnext/3.0` in the specified order for Ruby 2.5, and `.rbnext/2.7` and `.rbnext/3.0` for Ruby 2.6).
 
 ### Transpiled files vs. VCS vs. installing from source
 
@@ -445,6 +445,8 @@ AllCops:
 
 We currently provide support for Ruby 2.2, 2.3 and 2.4.
 
+**NOTE:** By "support" here we mean using `ruby-next` CLI and runtime transpiling. Transpiled code may run on Ruby 2.0+.
+
 Ruby Next itself relies on 2.5 features and contains polyfills only for version 2.5+ (and that won't change).
 Thus, to make it work with <2.5 we need to backport some APIs ourselves.
 
@@ -475,6 +477,8 @@ RUBY_NEXT_CORE_STRATEGY=backports ruby-next nextify lib/
 
 **NOTE:** For Ruby 2.2, safe navigation operator (`&.`) and squiggly heredocs (`<<~TXT`) support is provided.
 
+**IMPORTANT:** Unparser `~> 0.4.8` is required to run the transpiler on Ruby <2.4.
+
 ## Proposed and edge features
 
 Ruby Next aims to bring edge and proposed features to Ruby community before they (hopefully) reach an official Ruby release.
@@ -506,17 +510,13 @@ require "ruby-next/language/runtime"
 
 ### Supported edge features
 
-- "Endless" method definition (`def foo() = 42`) ([#16746](https://bugs.ruby-lang.org/issues/16746)).
-
-- Right-hand assignment (`13.divmod(5) => a,b`) ([#15921](https://bugs.ruby-lang.org/issues/15921)).
-
-- Find pattern (`[0, 1, 2] in [*, 1 => a, *c]`) ([#16828](https://bugs.ruby-lang.org/issues/16828)).
+No new features since 3.0 release.
 
 ### Supported proposed features
 
 - _Method reference_ operator (`.:`) ([#13581](https://bugs.ruby-lang.org/issues/13581)).
 
-- Shorthand Hash notation (`data = {x, y}`) ([#15236](https://bugs.ruby-lang.org/issues/15236)).
+- Shorthand Hash/kwarg notation (`data = {x, y}` or `foo(x:, y:)`) ([#15236](https://bugs.ruby-lang.org/issues/15236)).
 
 ## Contributing
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby-next
 version: !ruby/object:Gem::Version
-  version: 0.10.3
+  version: 0.12.0
 platform: ruby
 authors:
 - Vladimir Dementyev
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-09-28 00:00:00.000000000 Z
+date: 2021-01-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ruby-next-core
@@ -16,42 +16,48 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.10.3
+        version: 0.12.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.10.3
+        version: 0.12.0
 - !ruby/object:Gem::Dependency
   name: ruby-next-parser
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.0.0.1
+        version: 3.0.0.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.0.0.1
+        version: 3.0.0.3
 - !ruby/object:Gem::Dependency
   name: unparser
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 0.4.8
+        version: 0.5.6
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 0.6.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 0.4.8
+        version: 0.5.6
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 0.6.0
 description: "\n    Ruby Next is a collection of polyfills and a transpiler for supporting
   latest and upcoming edge CRuby features\n    in older versions and alternative implementations
   (such as mruby, JRuby, Opal, Artichoke, RubyMotion, etc.).\n  "