h a l f b a k e r yInexact change.
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
Before and after autofill
I tried to work out what was common to all work on a computer and then I realised it was just a large Rubik's cube and sliding puzzle game of moving things around | |
You have a start state (before)
You have an end state (after)
The computer works out the movements between those two states and infers all the intermediary states
I actually implemented this with A* graph search algorithm
Imagine a GUi where you can refer to things like a spreadsheet - this
is the before state.
Then you say where things should end up..
The computer works out how to move things from where they are to where everything goes.
Sliding puzzle codegen in Python
https://github.com/...zzle-codegen-memory
My A* implementation of this idea [chronological, Dec 06 2023]
Where does the idea stand in relation to *this* sort of thing?
https://www.reddit....anguage_with_graph/
[pertinax, Dec 06 2023]
[link]
|
| |
So ... you've reinvented declarative programming? |
|
| |
Am I to have a large rubix cube in my pocket, to use to look at kitten photos on twatfacemazongle? |
|
| |
You don't even really need the 'before' part. You just need the 'after,' which as we all know is 42. |
|
| |
Wow such a negative reaction :'( :'( cry cry |
|
| |
Yes, it's similar to declarative programming. |
|
| |
You say where things are to begin with and say where they should end up and all the instructions in the middle are generated. I would love this. |
|
| |
//Yes, it's similar to declarative programming.// |
|
| |
OK, so how is it *different* from declarative programming? In the idea, which is the new part? |
|
| |