Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
cloogle.org
cloogle.org
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Cloogle
  • cloogle.orgcloogle.org
  • Issues
  • #235

Closed
Open
Opened Oct 10, 2020 by Camil Staps@cstaps🚀Owner

No required contexts for functions

In the results of a unification search we apply the unifier found for each result to its type context, so that we can show a required context (and whether/where the relevant instances are found in the database).

However, because finaliseDB in Cloogle.DB.Factory does removeTypeContexts, this information is not available for normal functions. It is only available for class members and generics, which store the type contexts separately as well.

Because of this, the <*> result for :: (a b -> c) (a -> b) a -> c has a required context, but the ap result does not:

2020-10-10-162719_611x356

We need to check whether removeTypeContexts can safely be removed from finaliseDB.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: cloogle/cloogle-org#235