Timeline for Generate Pyramid Scheme code
Current License: CC BY-SA 3.0
27 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2017 at 16:44 | comment | added | Pavel | @Qwerp-Derp Huh, I'm blind then, I went threw it a couple times yesterday... | |
| Jul 21, 2017 at 8:57 | comment | added | clismique |
@Phoenix There are still (cdr(cdr t)) in the golfed code.
|
|
| Jul 21, 2017 at 3:12 | comment | added | Pavel |
@Qwerp-Derp They are present in the ungolfed code, but the golfed code uses cddr.
|
|
| Mar 24, 2017 at 10:13 | comment | added | clismique |
This is kinda late, but I found three (cdr(cdr ...))s in your code.
|
|
| Feb 28, 2017 at 23:27 | history | bounty awarded | NoOneIsHere | ||
| Feb 27, 2017 at 3:03 | vote | accept | Pavel | ||
| Feb 26, 2017 at 19:55 | comment | added | wizzwizz4 | A total bounty of 350 reputation is significant... but this answer deserves it. A Common Lisp answer to a question about constructing questions for a Lisp dialect... Wow. | |
| Feb 22, 2017 at 16:47 | comment | added | user63187 | @Azor1 congratz! +50 rep | |
| Feb 22, 2017 at 16:47 | history | bounty awarded | Community Bot | ||
| Feb 21, 2017 at 22:57 | comment | added | Neil Lindquist | @PrzemysławP yea it is, I must have missed it when I was golfing | |
| Feb 21, 2017 at 20:52 | history | edited | NoOneIsHere | CC BY-SA 3.0 |
added 62 characters in body
|
| Feb 21, 2017 at 11:09 | comment | added | user63187 | @NoOneIsHere yeah I took one look and started nopeing out. It is a cool problem and deserves a lot of rep. | |
| Feb 21, 2017 at 9:45 | comment | added | user65167 |
You wrote (cdr(cdr r)). Isn't (cddr r) same thing but shorter?
|
|
| Feb 21, 2017 at 6:48 | history | edited | Pavel | CC BY-SA 3.0 |
Added TIO link
|
| Feb 21, 2017 at 3:07 | comment | added | NoOneIsHere | @ChristopherPeart Depending on what happens the next 2 days, I was thinking +200-+300. This is a very challenging problem. | |
| Feb 21, 2017 at 2:14 | comment | added | user63187 | @NoOneIsHere you being for real? If so that is pretty cool | |
| Feb 20, 2017 at 17:28 | comment | added | NoOneIsHere | In addition to the +50 bounty, the fact that you posted this amazing answer will get another bounty from me. | |
| Feb 19, 2017 at 22:47 | comment | added | Neil Lindquist |
try using (format t "~d" ___) instead of (print ___). I think print outputs the text as lisp code, so the quotes are present and the backslashes need escaping whereas format prints the actual content.
|
|
| Feb 19, 2017 at 18:46 | comment | added | Pavel | I don't know common lisp, so maybe I'm doing it wrong, but it seems to be off a little: gist.github.com/pavelyay/dd7eea5c0dc8713b1327608ab9e780f7 (The link is in the gist, it's too long to fit in a comment) | |
| Feb 18, 2017 at 17:29 | comment | added | user63187 | Azor1 holy cow! Nice job. If nobody answers then you will get a 50 rep bounty from me. Try and golf as much as you can! | |
| Feb 18, 2017 at 15:58 | history | edited | Neil Lindquist | CC BY-SA 3.0 |
deleted 663 characters in body
|
| Feb 18, 2017 at 7:55 | comment | added | coredump |
... loop while (not x) is loop until x, (cdr (cdr x)) is (cddr x), (setf a b c d) is shorter than (setf a b) followed by (setf c d), etc. But this is already a good answer
|
|
| Feb 18, 2017 at 7:43 | comment | added | coredump |
Some tips for golfing CL: in loops, "for" can also be written "as"; you can remove spaces before and after parentheses and double-quotes; you can replace NIL by (); you can also use reader variables, sometimes
|
|
| Feb 18, 2017 at 7:01 | comment | added | user41805 | Welcome to PPCG and nice first answer! | |
| Feb 18, 2017 at 5:52 | comment | added | clismique | You should be able to golf off a lot of bytes by removing unnecessary spaces. | |
| Feb 18, 2017 at 5:28 | review | First posts | |||
| Feb 18, 2017 at 5:47 | |||||
| Feb 18, 2017 at 5:26 | history | answered | Neil Lindquist | CC BY-SA 3.0 |