Skip to content
Snippets Groups Projects

Serialization

Merged Jeremie Deray requested to merge serialization into master
1 unresolved thread
  • clean a bit NodeBase class.
  • wip serialization of NodeBase that exemplify the 'intrusive' serialization (Serializer class member) + test.
  • wip serialization of Eigen types (binary only) + test.
  • serialization TimeStamp + test.
  • serialization entry-point object is referred by typeid.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
72 unsigned int nodeId() const;
75 unsigned int nodeId() const;
73 76 std::string getClass() const;
74 std::string getType() const {return node_type_;}
75 std::string getName() const;
77 std::string getType() const;
78 std::string getName() const;
76 79
77 void setType(const std::string& _name){node_type_ = _name;};
80 void setType(const std::string& _type);
78 81 void setName(const std::string& _name);
79 82
80 virtual ProblemPtr getProblem(){return problem_ptr_.lock();}
81 void setProblem(ProblemPtr _prob_ptr) {problem_ptr_ = _prob_ptr;}
82
83 virtual ProblemPtr getProblem() const;
  • Jeremie: This const keyword in getProblem() prevents this method from being overloaded properly. In overloads, the problem_ptr_ in the class is sometimes written, and therefore this method cannot be const.

    This could have been designed differently. But what I want to say is that, by merging this MR, I could not compile the master branch. And therefore I wish to warn you about MR's not being properly tested.

    Did you compile this MR before doing the request?

  • Author Developer

    I did compiled and tested, 2 weeks ago when I opened it :s . Sorry for that.

    I have to insist on asking you to ask whomever is in charge of gitlab maintenance at IRI to setup a simple CI (continuous integration). This would automatically and constantly try to compile (possibly run tests) on every pull request / change, therefor save of lot of time and efforts to everyone and especially you.

  • Yes, we need CI. I ignore the procedure to implement it, and I guess I am too busy and lazy to go for it. But we need it.

    Besides, I reverted the design, removed all Derived::getProblem(), and made NodeBase::getProblem() both non-virtual and const, as it must be.

  • I am about to push it to master. EDIT: pushed.

    Edited by Joan Solà Ortega
  • Author Developer

    It is not quite simple to setup the CI, that's why you should grab someone from the IT department and ask this person to do it ^^.

  • Please register or sign in to reply
Please register or sign in to reply
Loading