Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turing Completeness - pending at a workflow level #4

Open
nmondal opened this issue Dec 25, 2022 · 1 comment
Open

Turing Completeness - pending at a workflow level #4

nmondal opened this issue Dec 25, 2022 · 1 comment

Comments

@nmondal
Copy link
Owner

nmondal commented Dec 25, 2022

We can not compute factorial.
I mean, technically we can, we can just create a nice script function as a body and it does would do it - something like this:

fact:
   body:  |
      def fact(n){ /*  write here */ }
      fact(n) // call

But this is cheating.
We may want to have a way to support this w/o having a Turing Complete scripting extension.

There is another way - using fork and then just having a join to keep on multiplying the value out of the fork.
That also, feels like cheating.
What we are really saying is that there is a lack of "self-referential" structure with halting.
Should we have it? We do not know.

https://stackoverflow.com/questions/315340/practical-non-turing-complete-languages

@nmondal
Copy link
Owner Author

nmondal commented Jan 18, 2023

On a related note, this problem I am not solving right now - because it has become a test bed of detecting - "DSA" and "CS Fundumentals" in a practical level - thanks to this question here: Quora Question

It is interesting to see how people would approach it, variously.
The approach differentiates their real knowledge and maturity level.
I expect someone at Staff Engineer level to crack it, but anything works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant