Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
RAPID-MIX_API
RAPID-MIX_API
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • 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
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • rapid-mix
  • RAPID-MIX_APIRAPID-MIX_API
  • Issues
  • #40

Closed
Open
Opened Oct 02, 2017 by Michael Zbyszyński@MikeZOwner
  • Report abuse
  • New issue
Report abuse New issue

Composition vs CRTP

MZ and Fabian discussed that JUCE users would be uncomfortable with the use of templates in the machine learning class.

We could use composition and a factory, which would probably be more familiar C++. Also, we could then do things like temporalClassification(HMM) rather than xmmTemporalClassification()

It's probably not worth it to rewrite this class right now.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: rapid-mix/RAPID-MIX_API#40