Arjun (Jul 17 2026 at 18:09): Arjun (Jul 17 2026 at 18:09):Hi @Anton , I have been looking at: issue#10178.
I have contributed 2 times before (both were simple good first issues).
This time, I took a Bug issue but I am having trouble understanding the flow of code.
The problem: [1,2,3,4,5].iter().take_last(3) causes segfaults. Same with roc repl and roc check. It doesn't cause problems with the take_first() or drop_first methods. After looking around some, I understood that take_last calls drop_first internally. The panic occurs at the LIR lowering part of the codebase. Since I have never implemented anything past a parser, I am not able to understand the flow of code here.
So how should I proceed here? I thought I'll find something simpler and found the following good first issue and was able to solve it with a one line change, issue#10041. So I am guessing that's for people very new to this, so I didn't add any PRs there.
Anton (Jul 17 2026 at 18:13):Hi @Arjun,
#10178 could be quite hairy. Feel free to submit a PR for #10041. When browsing issues I would avoid the segfaults, hangs and general memory issues for now but you can go through the issues and ask here if it would be good to take on with your current level of experience.
Arjun (Jul 17 2026 at 19:08):Sure Anton. Thanks for the reply. I'll work on something simpler then. #10041 is about changing "functions without body" errors to warnings. I changed the reporting from .runtime_error to .warning but that causes the compiler to crash. So I'm guessing there's more to it than just changing that.
Last updated: Jul 23 2026 at 13:15 UTC