@JoKing Another point is that most ASCII characters can be pushed onto the queue, which allows strings to be printed without escaping them.
(I worry that this will potentially fail after some developments.)
I am quite horrified at how hard this challenge is for Resource.
So maybe I can add a decoding instruction?
@Jono2906 (You are being too practical. :) ) Resource definitely needs loops in order to solve a wide variety of restricted source challenges, and I am currently trying to draft them as levels of abstraction.
If you are interested in it, the 1st level abstraction is simply the front 2 items in the queue, the 2nd level applies to the whole queue, and the 3rd level treats the history of the queue as a queue and applies to it as a whole.
room topic changed to Research: What happens when we all have a powerful restricted-source tool? (no tags)
room topic changed to Research: What will happen when we all have a powerful restricted-source tool? (no tags)
room topic changed to Research: The source code is a fine tool, but sometimes you misuse it. [class] [code-golf] [learning] [research] [resource] [restricted-source] [tips]
I am planning to make keyboard reversing the base encryption method, and all other methods need to call it.
room topic changed to Research: The source code is a fine tool, but sometimes you misuse it. (You use them not for their intended purpose, to present information; instead, restricted-source contestants are forced to change them.) [class] [code-golf] [learning] [research] [resource] [restricted-source] [tips]
I would like to describe my draft for "loops". (Simply just abstractions of symbols.)
In its initial level the + command maps to the whole queue. So [1 2 3] results in [6].
You might worry, where was the previous state of the queue?
They are pushed onto the history deque, and you may access the history by abstracting the instructions.
(I am proposing an inside-out operator m$, so let's use this as an example.)
So we abstract the operator using m!, the result is m!m$, therefore the history of the queue is flipped inside-out.
Anyway, I created this chatroom because I am trying to post a Resource answer to the main site, but then I realized I can't get into the chatroom.
Idea, manipulate the source code as if it were a queue
So conclusion of feature-requests: 1. Add different mappings. I might need some time to consider these mappings well, because currently reverse-keyboard sucks with the current challenges.
