I've just spent hours finally implementing variable names sharing among predicates, just to realize that this can't actually possibly work

For instance {+₁}ⁱ⁹ should increment an input 9 times

But since the output of predicate 1 is now globally shared as Var_Output_1, on the second increment it will already have a set output: the value of Var_Output_1 set during the previous increment.

The only way to make it work would be to have weird exceptions depending on the metapredicates which would be ugly as hell

cough {+₁⟩ⁱ⁹ cough

Would This be a valid answer to This question?

nvm

I understood final position as final board position

Actually

@Kroppeb I don't get it

The question has a definition for position: In this problem a position is defined simply by the configuration of the pieces on the board.

I'm talking about your "cough {+₁⟩ⁱ⁹ cough" not the challenge :p

ah

You can use that notation or something

Didn't even notice they weren't the same brackets

call it the big arrow or something

Nevertheless, I would rather die than have such a monstrosity of nature like {…⟩ in my language

I know you didn't want those but eh

:p

but ⟨...} could then have a shared output or something idk

Also I don't see where your idea is gonna be usefull

mmh missed this part though Ah, it has to be the final position that appeared at least twice before.

tio.run/##SypKTM6ozMlPN/r/3/5R2xQdg0edCx9u7c3IedS51Pj//…

Should I explain why my solution can be considered as valid?

@Kroppeb It's very, very useful when you need to pass multiple arguments to a predicate, or when e.g. you want to pass a constant argument to a map, etc.

instead of creating funky lists/zips

@Kroppeb I don't have much time to read the challenge right now, sorry

An easy solution to my problem (saying it here to remember it tomorrow): make it so that variables with no superscript are in local scope, just like before (including input/output), and variables with explicit superscripts are global. That way my example above with iterate would work normally, and you can access global variables (requires explicitely using superscripts every time though, but it's better than no global variables at all)