Survey on Refactorings for Elixir

Thanks, @josevalim! I really do appreciate you having pinned the post!

Done.

Btw. re [Struct field access elimination] see:

https://github.com/DaTrader/extructure

I’m confused about the meaning of the ‘relevance’ metric in the survey. For example, consider this question:

[ Transform a body-recursive function to a tail-recursive**]**.
This refactoring aims to convert a body-recursive function into a tail-recursive one, thus improving runtime performance due to the tail-call optimization provided by BEAM. More details and code examples here: [LINK]

I believe that the relevance of this very much depends on the particular function (does making it tail-recursive decrease readability and how much?) and, most importantly, on the expected input (do we expect infinite recursion and having a memory leak, or do we expect at most 10 stack frames to be kept at any time?). What should be my answer to this?

Hello, I understand your question. In fact, the relevance of a refactoring may depend on the application scenario, as you said.

I recommend that answers are always based on the worst case that the developer has experienced or is aware of someone having experienced. In this specific refactoring, as you said, it could be an infinite recursion, memory leak, etc.

In short, think something like this: “In general, can this bring me more advantages or not?”… The more advantage, the closer to 5.

For those who haven’t answered our survey yet, professor @adolfont made a short video showing our survey inside and how easy it is to answer it!

I would like to thank the great number of devs who have already participated in our survey. For those who have NOT yet participated and are interested, we will collect responses until April 3rd at 11:59 PM (UTC-3).