What would be the best approach to create a 448x448x4 3D list of 0s? I have two alternative 12 byters (4Å0¸448©и¸®и and 448©Å04ã®ô®∍), but I have the feeling this can be done in 10 or 9.. I'm just not sure what the correct builtins to use here are.. @Mr.Xcoder @Emigna @Adnan

I will probably have a "duhh, of course!..." moment as soon as one of you posts a <10 byter..

@KevinCruijssen I think (4Å02F¸448и) should work for 10 bytes

@Emigna Ah, that's indeed a duhh moment as I expected. ;) I had the feeling more appropriate builtins could be used besides the ¸и somehow, but maybe I'm mistaken. But good job finding a 10-byter, thanks.

Haven't found any way to get it sub-10. It seems unlikely that it's possible, but maybe someone will show me wrong :P

@KevinCruijssen I think this one should work for 9 bytes: 448LDδ4Å0.

@Adnan Ooh, that's clever!

This one works for 9 as well: ¾4Ƶ{·Dиии

but I haven't found an 8-byter

@Adnan Oh, both of those are nice. Completely forgot about δ. And didn't even knew the order on the stack should be reversed for и to work without the wrap-in-list. That's good to know. :) Thanks!

@Adnan Is Ƶ still useful now that we have Ž as well? Are the cases where Ƶ to get an integer is shorter than Ž. In this case of 448 both are 3 bytes: Ƶ{· vs Ž1Â. I've personally never used Ƶ, but are there any cases where Ž would be longer, or is it not useful anymore in the new version of 05AB1E?

I guess it could still be used if Ž ends with a digit and you want to push an integer right after it I guess, but apart from that?

@KevinCruijssen Well, for numbers between 101 and 356 it can be represented in two bytes

whereas that is not possible with Ž

@Adnan I thought 355 was max. What's 356?

@Emigna Yep you are correct, 355 is the max not 356