Menu

#103 Remove / Encapsulate boost::multi_array (removing boost #2)

0.2.2
done
nobody
None
nobody
2018-04-13
2017-08-21
Ulf Lorenz
No

Boost is a major drag when you want to compile anything, as the huge number of headers slows down the compilation considerably.

OperatorMatrix internally uses a boost::multi_array. This should either be hidden through a Pimpl-idiom, forward-declared in a portable way or replaced by a more mundane data structure. The goal is to remove the need for every user of OperatorMatrix to include boost::multi_array.

Measure the effect of this cleanup


  • replaced data structure by a normal, flat vector
  • no relevant effect on build times

Related

Tickets: #84

Discussion

  • Ulf Lorenz

    Ulf Lorenz - 2017-11-11
    • Milestone: Backlog --> 0.3 goal
     
  • Ulf Lorenz

    Ulf Lorenz - 2018-04-02
    • Milestone: 0.3 goal --> 0.2.2
     
  • Ulf Lorenz

    Ulf Lorenz - 2018-04-10
    • status: open --> assigned
    • assigned_to: Ulf Lorenz
     
  • Ulf Lorenz

    Ulf Lorenz - 2018-04-13
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -2,4 +2,9 @@
    
     OperatorMatrix internally uses a boost::multi_array. This should either be hidden through a Pimpl-idiom, forward-declared in a portable way or replaced by a more mundane data structure. The goal is to remove the need for every user of OperatorMatrix to include boost::multi_array.
    
    -Measure the effect of this cleanup!
    +Measure the effect of this cleanup
    +
    +----
    +
    +* replaced data structure by a normal, flat vector
    +* no relevant effect on build times
    
    • status: assigned --> done
    • assigned_to: Ulf Lorenz --> nobody
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.