Oddity where do/end block breaks expectations, but {} works fine?

[cfndsl]

Oddity where do/end block breaks expectations, but {} works fine?

[gonzalo-bulnes]

Hello @Integralist,

It look like a precedence issue, does this explanation make sense to you?

[howech]

I thing Gonzalo is right - its a ruby precedence thing. Calling functions
without using parans to indicate parameters can sometimes get you in
trouble.

On Tue, Mar 24, 2015 at 6:31 AM, Gonzalo Bulnes Guilpain <
[email protected]> wrote:

Hello @Integralist https://github.com/Integralist,

It look like a precedence issue, does this explanation
https://stackoverflow.com/a/6179505 make sense to you?

—
Reply to this email directly or view it on GitHub
#86 (comment).

[Integralist]

Turns out the issue is related to using push over <<. Using the double chevron fixed the problem. Previously where I had changed from {} to do/end seemed to not be the actual cause.

[stevenjack]

@Integralist you happy for this issue to be closed?

[Integralist]

Yup