Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I
iTasks-SDK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 77
    • Issues 77
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • 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
  • clean-and-itasks
  • iTasks-SDK
  • Issues
  • #226

Closed
Open
Created Jun 13, 2018 by Steffen Michels@smichelsOwner

Testing with generic fusion?

I'd suggest to test iTasks with generic fusion turned on. I enable it on default, as it significantly improves performance. It's not that mature yet, but if we test it with iTasks we put some pressure on making it more stable.

A recent change breaks generic fusion (see https://gitlab.science.ru.nl/clean-and-itasks/clean-compiler/issues/9), it would be great to see that directly in the CI tests.

Generally, I'd suggest to turn it on in all .prj.default files.

What do you think @baslijns, @mlubbers?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None