[HN Gopher] Emit-C: A time travelling programming language
___________________________________________________________________
Emit-C: A time travelling programming language
Author : doppp
Score : 37 points
Date : 2024-11-12 15:10 UTC (3 days ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| unquietwiki wrote:
| Submitted to r/altprog ; I love a language that can murder
| variables, heh.
| roarcher wrote:
| This one can murder its own grandfather.
| cyanmagenta wrote:
| I am going to be harsh here, but I think it's necessary: I don't
| think anyone should use Emit-C in production. Without proper
| tooling, including a time-traveling debugger and a temporal
| paradox linter, the use case just fails compared to more
| established languages like Rust.
| doormatt wrote:
| No one is claiming this is necessary. It's a toy language built
| for fun.
| mygrant wrote:
| Woosh
| porcoda wrote:
| Given how often people seriously say things like the top
| level comment being responded to around here, an explicit
| /s is almost necessary since it can be hard to distinguish
| from the usual cynical dismissive comments.
| hathawsh wrote:
| Please ELI5... I know there's a joke in there, but I'm
| missing it.
| skavi wrote:
| The humor lies in the inherent absurdity of the critique
| itself. Obviously no one will use this in production.
| There's nothing especially clever you're missing.
| deadbabe wrote:
| For the _real_ computer scientists out here, what would time
| complexity notation be like if time traveling of information was
| possible (i.e. doing big expensive computations and sending the
| result back into the past)?
| openasocket wrote:
| Surprisingly there is prior work on this!
| https://www.scottaaronson.com/papers/ctchalt.pdf . Apparently a
| Turing Machine with time travel can solve the halting problem
___________________________________________________________________
(page generated 2024-11-15 23:00 UTC)