…Whats slot 114 though?
Slot 14 is a variables list:
You can make it varadic:
So you just cant do that via metaprogramming? Weird.
I remember jens talking about the variadic slot 14 once; not sure where, though.
This isn’t a bug. Since slot 14 is already variadic, adding 100 to make it variadic simply doesn’t make sense, and although it was possible in the past that has now been patched, it seems. Setting the slot to other things seems to work:
Interesting. I do remember jens saying he just hadn’t gotten around to disabling such combinations because of all the other stuff he was working on, however.
Whoops. I meant 112, thx!
Slot 112 is variadic upvars (not the supported variables input), and it can only be created with metaprogramming, it’s impossible (kinda) in the gui.
Slot 114 is the variadic variables input, which can be pretty easily created in the gui, but is disabled with metaprogramming
I personally think that both of these should be blocked in both the ui and metaprogramming because they’re clearly not supported, and you can’t really do much with either (directly) in the block definition.
I feel like they don’t really need to be blocked since, well, no beginner is going to have any trouble with this or confusion.
One of the new libraries uses slot 112 IIRC.
I think they use the parameter slot (like upvar but doesn’t actually declare the variable). However, the OOP library has variadic upvars in a group input slot.