Activity for trichoplax
| Type | On... | Excerpt | Status | Date |
|---|---|---|---|---|
| Edit | Post #284894 |
Post edited: Typo in title |
— | about 1 year ago |
| Comment | Post #287139 |
Thank you! And thanks for the saved byte - it made me realise I should adjust my generating code to sort by fruit length in bytes (which resulted in a similar replacement to your suggestion, for the same number of bytes). (more) |
— | about 1 year ago |
| Edit | Post #287139 |
Post edited: Move golfing credit to immediately after the code |
— | about 1 year ago |
| Edit | Post #287139 |
Post edited: Save 1 byte thanks to msb's comment |
— | about 1 year ago |
| Comment | Post #289782 |
One thought which makes me lean towards keeping it a single question:
The line between different types is not always clear. Some languages have floating point for non-integer values, other languages have fixed point, or an arbitrary precision decimal or rational type. Since there might be some ove... (more) |
— | about 1 year ago |
| Comment | Post #289782 |
So I think splitting answers will be needed even if this is split into more questions. I don't personally see a need to split this question, but I don't see a problem with splitting it either. (more) |
— | about 1 year ago |
| Comment | Post #289782 |
Similarly if an answer gives 2 rules for string length, they cannot be separately voted on. For example, if someone says "string inputs only have to be supported up to N characters" but also says "for language X it's M characters" then someone may agree with the general rule but not with the exceptio... (more) |
— | about 1 year ago |
| Comment | Post #289782 |
I was commenting as a hint to answerers. I don't see a problem with several related rules being discussed under one question - that's similar to how the other "default-rules" questions work.
The concepts you have listed in the question are all very closely related, so I like them being in one ques... (more) |
— | about 1 year ago |
| Comment | Post #289782 |
It might be easier to see community consensus if each proposed rule is posted in its own answer to allow separate voting. This will then be similar to the other Meta questions tagged "default-rules". (more) |
— | about 1 year ago |
| Edit | Post #289782 |
Post edited: Make title clearer and add default rules tag |
— | about 1 year ago |
| Suggested Edit | Post #289782 |
Suggested edit: Make title clearer and add default rules tag (more) |
helpful | about 1 year ago |
| Comment | Post #289679 |
That's a good point. Currently the only restriction I can find is against non-free languages, and that only applies to one challenge type (so not to code golf):
- [How free is "free" for cops and robbers?](https://codegolf.codidact.com/posts/282856)
This doesn't change my opinion (I would still... (more) |
— | about 1 year ago |
| Suggested Edit | Post #284894 |
Suggested edit: Typo in title (more) |
helpful | about 1 year ago |
| Comment | Post #289679 |
It's tempting to think that multiplying by 4 would always be enough, but in general the duration on one computer will not scale linearly to the duration on another computer. For different code the scaling factor will be different (even for different solutions to the same challenge).
I agree it cou... (more) |
— | about 1 year ago |
| Comment | Post #289679 |
The time limit is a big part of my concern. Everyone can agree on how many bytes there are, but different computers will have different speeds and therefore different outputs if based on run duration. (more) |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Tidy up intro wording |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Remove accomplished requirement to have all 66 compass points in the test outputs |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Remove ambiguity by not using the word "set" in the overview. |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Clarify secondary compass points |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: More test cases |
— | about 1 year ago |
| Edit | Post #289678 |
Post edited: Add finalized tag so it can be excluded by the filter in the question list |
— | about 1 year ago |
| Suggested Edit | Post #289678 |
Suggested edit: Add finalized tag so it can be excluded by the filter in the question list (more) |
helpful | about 1 year ago |
| Comment | Post #289678 |
Finding test cases that work under several different types of rounding sounds like a good compromise - I hadn't considered that. This might allow you to write just one set of test cases that works for all approaches, which sounds much easier to work with. (more) |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Mention possible Voronoi map diagram |
— | about 1 year ago |
| Comment | Post #289679 |
Generally I prefer a challenge to be specified in terms of its output, rather than its internal workings. So "the output must meet these criteria" rather than "you must use this algorithm". It is easy to verify that the output is correct, whereas it is difficult to prove that a particular algorithm i... (more) |
— | about 1 year ago |
| Edit | Post #289678 |
Post edited: Replace "a" with "an" before vowels |
— | about 1 year ago |
| Comment | Post #289678 |
The other problem with having many permitted approaches is that it becomes more difficult to write test cases. I recommend adding test cases to make it easier for people to check their own and each other's answers, particularly if unexpected edge cases appear. It is still possible to write test cases... (more) |
— | about 1 year ago |
| Comment | Post #289678 |
I never know how much flexibility to include in a challenge. I want the challenge to be flexible enough to allow as many people and languages as possible to enter. I also don't want too much flexibility as this puts a burden on the people solving the challenge.
For example, if there are 2 permitte... (more) |
— | about 1 year ago |
| Suggested Edit | Post #289678 |
Suggested edit: Replace "a" with "an" before vowels (more) |
helpful | about 1 year ago |
| Comment | Post #287082 |
I wanted a unique name for each compass point, in the same way that real compass points have NW but not WN.
I'll think about whether that requirement could be dropped, and I'll also think about how it could be better explained if I keep it. (more) |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Specification golfing |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Subdivide definitions section |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Adjust test case format to allow for multiple valid outputs |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Add heading to isolate brief intro |
— | about 1 year ago |
| Edit | Post #287082 |
Post edited: Use integer inputs to be inclusive of more languages and approaches |
— | about 1 year ago |
| Comment | Post #289604 |
For anyone else testing this, note that `bit_count` requires Python 3.10 or higher. (more) |
— | about 1 year ago |
| Comment | Post #289604 |
```text
Input: 17609903308800 Expected: 36 Actual: 36
Input: 18441077155848519679 Expected: 1 Actual: 0 MISMATCH
Input: 18440988645153550335 Expected: 2 Actual: 1 MISMATCH
Input: 9214294468855857151 Expected: 1 Actual: 1
Input: 18300371588261871615 Expected: 1 Actual: 1
Input:... (more) |
— | about 1 year ago |
| Comment | Post #289604 |
```text
Input: 0 Expected: 64 Actual: 64
Input: 18446744073709551615 Expected: 0 Actual: 0
Input: 12273903644374837845 Expected: 0 Actual: 14 MISMATCH
Input: 9819010546270478865 Expected: 16 Actual: 9 MISMATCH
Input: 9223372036854775808 Expected: 61 Actual: 61
Input:... (more) |
— | about 1 year ago |
| Comment | Post #289604 |
(Note that the test case failures are not related to the suggested change - they are already failing.)
In case it's helpful (or in case I've made a mistake), the code I used for testing is [available as a GitHub gist](https://gist.github.com/trichoplax/bc5dcc53c6bdd111a3a51c294fc86df9). It gives t... (more) |
— | about 1 year ago |
| Comment | Post #289604 |
The good news is you can save a byte by not putting the `return` on its own line.
The bad news is some of the test cases fail. (more) |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Mark as finalized |
— | about 1 year ago |
| Edit | Post #289542 | Initial revision | — | about 1 year ago |
| Question | — |
Word suggesting Suggest a word from a word list, given a string. Motivation Imagine typing a word one letter at a time, and seeing a suggested word after each letter is typed. At first the suggested word is simply the first word in the word list that matches, but once a word has been suggested it is assumed that... (more) |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Clearer example headings |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Make input section more precise |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Make example wordings more precise |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Add description of test case format and quotes around outputs |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Add test cases |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Unordered list formatting fix |
— | about 1 year ago |
| Edit | Post #288755 |
Post edited: Add edge case to algorithm and add extra examples |
— | about 1 year ago |