nepalez (Andrew Kozin)
- Login: nepalez
- Email: andrew.kozin@gmail.com
- Registered on: 06/18/2015
- Last sign in: 07/31/2015
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 3 | 3 |
Activity
07/02/2015
-
01:05 PM Ruby Feature #11325 (Rejected): Block is passed to initializer implicitly even when I asked not to.
- This works as expected:
~~~ruby
class Foo
attr_reader :block
def initialize(&block)
@block = block
end
end
foo = Foo.new { :foo }
foo.block.nil?
# => false
~~~
But then I'm trying to stop passing a block to ...
06/23/2015
-
- Thank you, Nobuyoshi, for your answering. Now I see the reason.
When I told that `Foo::Bar::Qux` is "closest" to `Foo::Baz` I meant that in a namespace:
~~~ruby
module Foo
module Baz
p Bar::Qux
end
end
# => Foo::Bar::...
06/22/2015
-
- ~~~ruby
module Foo; end
module Foo::Baz; end
module Bar; end
module Bar::Qux; end
Object.const_get "Foo::Baz::Bar::Qux"
# => Bar::Qux
~~~
Why on earth it is found at all?
It seems pretty weird to me.
The real problem aris...
06/19/2015
-
- Not, in my examples (from the initial post) it does not do that, but something different. Namely, it doesn't assigning a **new** proc (that would be OK)
Instead, the interpreter looks around in search **what else** it could use when I...
06/18/2015
-
- I'd expect Ruby to do any of two options:
* Either provide a method with empty proc (`Proc.new`)
* Or call `SyntaxError` as a strict way to ask for the programmer's intention
I think any of these options could follow POLA better t... -
- This feature buzzes and wiggles aerials like a bug.
I cannot see why is it needed for your example. It is pretty explicit and has no hidden calls. Both the `yield` and `Proc.new` are used intentionally, while in my examples they weren... -
- That is how it works:
module Test
def self.build(&block)
klass = Class.new(Object)
klass.__send__(:define_method, :foo)
klass.__send__(:define_method, :bar)
klass
end
end
...