Skip to main content
Code Golf

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 1
    \$\begingroup\$ Also, some more test cases would be useful. \$\endgroup\$ Commented Apr 28, 2017 at 15:30
  • 1
    \$\begingroup\$ @Tutleman Yes, you can take 0 1 2 for instance \$\endgroup\$ Commented Apr 28, 2017 at 17:36
  • 1
    \$\begingroup\$ Wait, can we take e.g. !_#$%&-()*}w[vz0123456789SsW]VZ@AXJE>UIDCHTNMBRL"POYGK<QF:/\=^{`axje.uidchtnmbrl'poygk,qf;?|+~ as the input for the Dvorak keyboard? That would trivialize the challenge... How about introducing a length restriction or something similar? \$\endgroup\$ Commented Apr 28, 2017 at 18:38
  • 1
    \$\begingroup\$ @EriktheOutgolfer But then you could take e.g. !_#$%&-()*}w[vz0123456789SsW]VZ@AXJE>UIDCHTNMBRL"POYGK<QF:/\‌​=^{`axje.uidchtnmbrl‌​'poygk,qf;?|+~ as input \$\endgroup\$ Commented Apr 29, 2017 at 11:05
  • 1
    \$\begingroup\$ @ETHproductions Yes you could use those characters as inputs, although the layouts must not depend on them at all to be constructed. The only use for them would be to choose which layout to use. 10 bytes is a fixed limit (IMO too short), that's why I don't like it. And yes you say bytes not chars. I think this should've been sandboxed for more time. \$\endgroup\$ Commented Apr 29, 2017 at 13:59