What effect would a transpose builtin have on Charcoal? 35 of my Charcoal answers contain the word "transpose", but some of them don't seem to be relevant or will only save at most one byte. Of the other answers:

• 3 bytes are saved:
  • by 255406 and 255452 because the array was of height 2 and known width
  • if the answer transposes an array of known width which has to be mapped over anyway, e.g. 165088, 235913, 243142
• 4 bytes are saved if the answer transposes an array of unknown width which has to be mapped over anyway, e.g. 226778
• 5 bytes are saved:
  • by 241418 because although the array was a duplicated expression the array has to be mapped over anyway
  • if the answer transposes an array of known width, e.g. 201502, 211738, 216423, 221270, 241716, 266011
• 6 bytes are saved if the answer transposes an array of unknown width, e.g. 169410, 222934, 241967, 255100, 256984, 265782
• 7 bytes are saved:
  • by 213927 because although the array is of known width the newer version of Charcoal can then apply vectorisation instead of mapping
  • by 235875 because it currently uses a different storage format to reduce the byte count of the two "transpose" operations
• 8 bytes are saved:
  • by 195368 because although the array is of unknown width the newer version of Charcoal can process the results more efficiently
  • by 258164 because although the array is of unknown width it doesn't have to be stored in a temporary variable
• 12 bytes are saved by 219441 because although the array is twice of known width the newer version of Charcoal can then apply vectorisation instead of mapping