Oh interesting, I thought that was a typo 😂. I was playing around with characters after I wrote this and found something that I think looks a little better than the "}" thing: ```ruby markdown <<~___ # Hello How are you do...bradgessler (Brad Gessler)
Same reason you can conjure up a Proc via `-> {}` — the syntax looks cleaner and you don't have to stop and try to name it. Not having to name a string is a pretty big boost in terms staying in the flow. The second thing: it looks ...bradgessler (Brad Gessler)
I have code that looks like this in an application: ```ruby ContentSlide(title: "Why Phlex?"){ Markdown <<~MARKDOWN * Because its fun * Because its super-de-dooper MARKDOWN }, ``` The "squiggle" HEREDOCs strips the...bradgessler (Brad Gessler)
I'm working with some code in Phlex that would benefit from introspecting the name of the HEREDOC. Here's what I currently have: ```ruby ContentSlide(title: "Why Phlex?"){ Markdown <<~MARKDOWN * Because its ...bradgessler (Brad Gessler)
I find debugging and certain meta-programming tasks challenging because there's no explicit APIs for accessing certain types of arguments in Ruby. Here's some example code: ```ruby def splats(one, *, two: nil, **, &) # These wo...bradgessler (Brad Gessler)
# Premise Sometimes when I'm creating a method for an API, I'd like to do pattern matching against the arguments. Today I have to do something like this: ```ruby def foo(*args, **kwargs, &block) case { args:, kwargs:, block: ...bradgessler (Brad Gessler)
Reduce the number of steps required to install a gem from two steps to one by using `bundle add` https://github.com/rubygems/rubygems/commit/2c968420cdbradgessler (Brad Gessler)