Discussion is not necessary, but could be useful for critiquing a pattern. This would be useful for people who are proposing a pattern to the community or for people who want to gather feedback on an experiment.

No worries, I was just thinking that this issue should probably get necro'd back to open.

I took the liberty of editing this answer because it's already accepted

"When an OP rejects your edit, please do not edit it back in!" Correspondingly, when a user repeatedly does try to edit, understand that something in your framing isn't working right, and you should reconsider it.

Thank you. I appreciate your reply after all this time.

VII, after the map block, consider arr.each_with_object([]) do |(converted_val, orig_val),uniques|...end.

I know you acknowledged your response was late and you're just trying to help but please don't resurrect very old threads.

While statistical skills are required to test hypotheses, analysts are your best bet for coming up with those hypotheses in the first place. For instance, they might say something like “It’s only a correlation, but I suspect it could be driven by …” and then explain why they think that. This takes strong intuition about what might be going on beyond the data, and the communication skills to convey the options to the decision-maker, who typically calls the shots on which hypotheses (of many) are important enough to warrant a statistician’s effort. As analysts mature, they’ll begin to get the hang of judging what’s important in addition to what’s interesting, allowing decision-makers to step away from the middleman role.

I wish you would have contributed back to this project instead of forking or at picked a different name

I'm happy to try to reach agreement with you, but this isn't the right place. Feel free to invite me to a more appropriate forum.

We prefer Freshconnect for ticket related discussions because it maintains the context and always remains part of the ticket. In Slack, these discussions get lost in threads within channels.

View your discussions easily, without getting lost in multiple threads of conversations.

Is there a reason not to do caused-by stack trace printing? Or has it just not been implemented by anyone yet?

7 years after this question, I believe the correct answer is

I realize I'm 6 years late to this party, but

FYI for later travellers, it looks like the comment in question by @FreeSoftwareServer has been removed.

For every question you might have, please create a discussion thread, not a single comment. This makes it a bit easier to see and reply to the question, instead of questions and answers getting mixed together: