Implement a function \$f\$ (as a function or complete program), such that
\$
\displaystyle\lim_{n\rightarrow \infty} f(n)
\$
Is not a computable number.
Answers will be scored in bytes with fewer bytes being better.
IO formats
Your answer may be in any of the following formats
A program or funct...
@hyper-neutrino The thing is that asList takes ...T, and String[] can be turned into ...String, but int[] can't be turned into ...int because int isn't a subclass of Object. Since int[]is an Object, it interprets that as ...int[]
I don't like that a T[] can be used as varargs directly instead of using something like * or ... to explicitly indicate that it's not a single argument
i do not know much about ruby but i don't think it places extreme enough emphasis on inheritance and encapsulation and whatever the other words are that computer science education thinks are of some profound importance
there's a certain extent to which the more imperative something is the more intuitive it is to someone with no experience whatsoever but the more things you're doing imperatively the harder it is to actually reason about them
Most people have very little memory of how hard it was to learn programming, so when they have to learn everything a new way in Haskell, without being able to rely on their existing knowledge it seems really hard, when it really is no harder than any thing they have been working with.
you don't need maths experience: a function is a thing that takes inputs and outputs something as a result you can feed functions into other functions ez
@rak1507 Lol I didn't even understand normal functions (i.e., functions taking values as input) at first, teaching me higher-order functions would've driven me crazy
@UnrelatedString Right, but Python should only be a tool for teaching the very basics. It's pretty easy to teach - I made a small tutorial with no difficulty
Having been a CS tutor for classes taught in Python, and Haskell. I can say that I did not see a significant difference in the difficulty students had with either language. Learning to program is hard.
SQL is a beautiful language. The lack of case sensitivity has to be my favorite part about it - you can truly express how you're feeling with the language. If I'm angry, I can shout. If I'm calm, I can talk normally or even whisper. It's almost like a form of art.
This may not be the most rational opinion since I am currently writing python code for work. But I prefer SQL over Python. Python is an abomination on this earth.
I have nightmares that there is an easily avoidable type error hiding on some yet unexecuted line of python code that will cause a severe outage when encountered.
@rak1507 The problem is that nothing is checked at compile time. So a silly mistake can make it all the way to production. Simple errors at the level of types should not make it past compilation.
JS pain is different from SQL pain...JS pain is sharp but quickly subsides, SQL pain is like a boulder on your arm and you have to either keep feeling pain or cut off the affected part and ask someone for help
@RedwolfPrograms python is like having a genetic disease that is fine now but 5 years later randomly kills you because you accidentally passed the wrong type into something except because of duck typing it was never noticed
The problem with python is that if you program in it long enough its flaws just sink in the the background and you start think Python is good. But if you program in a language that is actually good each little flaw sticks out like a sore thumb and you keep wishing for something better, something with more power and elegance. Then one day you snap back to realize you are using a theorem prover to grep for files.