bindable_block 0.0.5 → 0.0.5.1

data/README.md

@@ -12,6 +12,45 @@ greeter.bind(User.new "Josh").call # => "Welcome, Josh"
 
 [Here](https://github.com/JoshCheek/surrogate/blob/eb1d7f98a148c032f6d3ef1d8df8b703386f286d/lib/surrogate/options.rb#L32-34) is an example.
 
+## Where the abstraction leaks
+
+Bindable block does something that isn't possible in Ruby.
+It does this with black magick. Unfortunately, that abstraction
+will leak in the case of return statements. Return statements in
+blocks will return you from the containing method.
+
+```ruby
+def meth
+  Proc.new { return 1 }.call
+  2
+end
+
+meth # => 1
+```
+
+
+Return statements in lambdas will return you from the lambda.
+
+```ruby
+def meth
+  lambda { return 1 }.call
+  2
+end
+
+meth # => 2
+```
+
+You would expect a bindable block to continue to behave like the
+former example, but it will actually behave like the latter example.
+
+At present, I can only think of two ways to fix this:
+
+1) It might be possible to rewrite the AST with ripper.
+2) It is probably possible to write this in C.
+
+Neither of these are high on my priority list.
+
+
 ## Installation
 
 Add this line to your application's Gemfile:

data/README.mountain_berry_fields.md

@@ -14,6 +14,49 @@ greeter.bind(User.new "Josh").call # => "Welcome, Josh"
 
 [Here](https://github.com/JoshCheek/surrogate/blob/eb1d7f98a148c032f6d3ef1d8df8b703386f286d/lib/surrogate/options.rb#L32-34) is an example.
 
+## Where the abstraction leaks
+
+Bindable block does something that isn't possible in Ruby.
+It does this with black magick. Unfortunately, that abstraction
+will leak in the case of return statements. Return statements in
+blocks will return you from the containing method.
+
+```ruby
+<% test 'proc behaviour', with: :magic_comments do %>
+def meth
+  Proc.new { return 1 }.call
+  2
+end
+
+meth # => 1
+<% end %>
+```
+
+
+Return statements in lambdas will return you from the lambda.
+
+```ruby
+<% test 'lambda behaviour', with: :magic_comments do %>
+def meth
+  lambda { return 1 }.call
+  2
+end
+
+meth # => 2
+<% end %>
+```
+
+You would expect a bindable block to continue to behave like the
+former example, but it will actually behave like the latter example.
+
+At present, I can only think of two ways to fix this:
+
+1) It might be possible to rewrite the AST with ripper.
+2) It is probably possible to write this in C.
+
+Neither of these are high on my priority list.
+
+
 ## Installation
 
 Add this line to your application's Gemfile:

data/lib/bindable_block/version.rb

@@ -1,3 +1,3 @@
 class BindableBlock
-  VERSION = "0.0.5"
+  VERSION = "0.0.5.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bindable_block
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.5.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-06-09 00:00:00.000000000 Z
+date: 2012-06-18 00:00:00.000000000 Z
 dependencies: []
 description: instance_exec can't pass block arguments through. Use a bindable block
   instead.