yancouto/functional

functional programming game

functional's Issues

Count reductions

Count reductions in solution

Better printing

Printed expressions are better than what they used to look, but still pretty ugly.

We should use x over x_0 where possible, and there's no need to rename variables if they don't collide (that is, unless they're unbound variables with different ids).

Also, let's get rid of unnecessary parenthesis as much as possible.

Multiple solutions

Let's design with that in mind out of the box

Implement hint

Box instead (or below) extra info that you need to click to see the hint.

The documentation isn't good enough.

The explanations for the game are hard to understand, and need to be replaced. For many of the first puzzles I spent more time trying to figure out the syntax of the language than I did trying to figure out the solution to the puzzle.

Save game

Add sentinel to lists

Currently lists have no sentinel, so it's hard to iterate on them. Adding a FALSE at the end should be enough, like here. May make code slightly harder though.

We would need to change the definition of numbers as well.

Section for pairs and arrays?

Probably can shove it all in a section? Probably need to explain recursion here as well.

Better debugging

We'll definitely need some step by step interpreting, and showing this to the player.

Improve editor

Right now it's a quite shitty replace editor, will definitely need improving.

Constants box

Show a text box, probably next to the editor, showing the constants you know, maybe with explanations.

Only use constants from levels you solved

You should be able (already are) to solve levels in any order. However, it would be neat if you could only use constants from levels you solved.

This could also create some strategy in the order you solve the levels, which is cool. I tried to organize by the order I think is better, but it is different for everyone.

Last point:

• When you're solving a level, you can only debug test cases that don't have constants you don't know. (You can still solve the problem, though.) This makes it so you can't accidentally learn solutions by looking in future problems, without making things too hard.

Use keyboard everywhere

Should be possible to use keyboard everywhere (or almost, at least)

• Clicking buttons in "text box with options", that may be the most disruptive

Don't write outside of text editor box

Right now if you go over the box it will still print stuff.

A bit harder because of the Xi editor, but should be possible.

Level complete

For now, we just show a "WA/AC" text, we should have proper stuff for that.

Section for other numerals

Can look exactly the same as cooks numerals, I wonder how different it is to solve the problems.

Section for Church'snumerals

N := f:x: f (f (f ... (f x)))

Settings screen?

What could go here? Nothing is really customizable so far.