Skip to content

Investigate forcing loops to have a well defined exit condition to allow for more powerful static analysis #33

Closed

Description

@Isaac-Leonard

Some languages such as Alanlang and some C coding standards such as those used at JPL NASA enforce that any looping code has a well defined exit condition for loops to enable more powerful static analysis.
While possibly overly strict This seems like it would be a useful feature for borrowScript to have although it would need to be well implemented to not limit dinamicness too much.
These languages and standards also generally limit the depth of recursion however I believe that enforcing that cleanly would be harder as programmers would have to keep track of how far down the recursion stack they were as to not cause an error.
Also this technically already exists in V8 and Firefox javascript engines as they haven't implemented tail call optimisation yet although that doesn't really count.

Activity

  1. SuperSonicHub1 commented on Oct 23, 2021

    @SuperSonicHub1

    What do you mean by this? Something like C's noreturn macro?

  2. Isaac-Leonard commented on Oct 23, 2021

    @Isaac-Leonard
    ContributorAuthor

    Not exactly no although that does sound useful.
    This mainly focuses on the ability to parallelise however is still relevant to static analysis:
    https://alan-lang.org/the-turing-completeness-problem.html
    Heres the nasa coding standards I was referencing too:
    https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code#Rules
    The main ones I'm thinking about here are the first two.

  3. SuperSonicHub1 commented on Oct 24, 2021

    @SuperSonicHub1
  4. Isaac-Leonard commented on Oct 29, 2021

    @Isaac-Leonard
    ContributorAuthor

    Not exactly.
    The point would be for it to be analysed at compile time, so the program doesn't get into any unexpected infinite loops.

  5. locked and limited conversation to collaborators on Feb 17, 2023
  6. converted this issue into a discussion #71 on Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions