[00:06:37] it appears in python that typed lists are represented perfectly fine and returning [a, b, c] or anything of the sort does properly return a typed list on the wikifunctions side [00:06:44] but it doesnt appear to be the case for maps [00:07:40] oh nevermind, it does actually seem to properly return it [00:08:19] the issue then is just that theres no way to add elements to it inside of the browser like you can with typed lists and the little plus buttons [00:35:53] My understanding is that typed maps are not officially supported yet. So I haven't personally even tried to use them (re @wmtelegram_bot: is the typed map function usable in any capacity currently) [00:36:06] that sucks [00:36:30] im trying to make functions for them right now but its very difficult and i dont know how to work with it [00:36:53] considering all it usually gives me is more argument value errors im assuming they just arent workable with at the moment [00:38:36] merely passing them in seems to give the error so im assuming its an issue with the fact that the frontend doesnt support them right now [00:38:43] Z24603 [01:43:26] I'd recommend against this because their behaviour may change when they are officially released. (re @wmtelegram_bot: im trying to make functions for them right now but its very difficult and i dont know how to work with it) [01:57:35] okay fair [01:58:23] i only did like five and theyre all rudimentary stuff if thats okay [01:58:45] i wont touch it anymore though. would still be nice to be able to use maps though [01:59:59] "Stateless" means there's no way to create and store a variable modified across loops in a composition besides recursion, right? [02:06:48] Yes I think that is an implication of "stateless". (re @wmtelegram_bot: "Stateless" means there's no way to create and store a variable modified across loops in a composition besides recursion,...)