Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pakcs
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • curry
  • pakcs
  • Issues
  • #1

Closed
Open
Opened Dec 16, 2015 by Michael Hanus @mhOwner

Wrong solutions for combination of blackhole and non-determinism

Consider the following program:

main = let x = True ? fcase x of True -> False in x

With respect to the corrected natural semantics of FlatCurry, this defition has only one value: True. However, PAKCS computes both True and False as solutions before it enters an infinite loop:

blackhole> main
True
False
Prolog interruption (h for help)?

In contrast, the KiCS2 computes only the single value True before it enters the infinite loop.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: curry/pakcs#1