Timeline for Simple Brainfuck Interpreter in Rust
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2020 at 13:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 6, 2019 at 9:00 | history | tweeted | twitter.com/StackCodeReview/status/1192003832022274050 | ||
| Nov 2, 2019 at 12:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 5, 2019 at 12:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 7, 2019 at 11:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 5, 2019 at 10:17 | answer | added | hellow | timeline score: 1 | |
| Feb 5, 2019 at 8:56 | comment | added | DimChtz | @hellow No worries. My bad, I would think it's a link to wikipedia as well lol | |
| Feb 5, 2019 at 8:37 | history | edited | DimChtz | CC BY-SA 4.0 |
added 119 characters in body
|
| Feb 5, 2019 at 8:36 | comment | added | hellow | No! As said, it is the correct way. Always post the related to to stackexchange, so it does not rely on external sources. But it's a extra step so it is easier for me to get and inspect the code, instead of doing copy&paste 8 times and setting up the repo correctly. | |
| Feb 5, 2019 at 8:35 | comment | added | DimChtz | @hellow Sorry, should I delete this? Yes, I added a link the repository in case it's hard to read the code from the post. | |
| Feb 5, 2019 at 8:32 | comment | added | hellow | Do you have a repository for this? It is correct, that you post the code here, but it's a bit cumbersome to scrap the code from this post. | |
| Feb 5, 2019 at 8:27 | history | asked | DimChtz | CC BY-SA 4.0 |