This bugzilla service is closed. All entries have been migrated to
Bug 1064 - Question regarding Ref<SparseVector>
Summary: Question regarding Ref<SparseVector>
Alias: None
Product: Eigen
Classification: Unclassified
Component: Sparse (show other bugs)
Version: 3.3 (current stable)
Hardware: All All
: Normal Feature Request
Assignee: Nobody
Depends on:
Blocks: 3.3
  Show dependency treegraph
Reported: 2015-09-15 03:03 UTC by Benjamin Chretien
Modified: 2019-12-04 14:54 UTC (History)
2 users (show)

Test with Ref<SparseMatrix/SparseVector> (1.85 KB, text/x-c++src)
2015-09-15 03:03 UTC, Benjamin Chretien
no flags Details

Description Benjamin Chretien 2015-09-15 03:03:37 UTC
Created attachment 604 [details]
Test with Ref<SparseMatrix/SparseVector>


In the Eigen 3.3-alpha1 pre-release, I noticed that support for Ref<SparseMatrix> was added (which is greatly appreciated!). While doing a quick check to see if one of our projects, RobOptim (, was working with the changes made to Eigen (we rely heavily on Eigen features such as Ref, sparse matrices/vectors etc.), I realized that Ref<SparseVector> is currently not possible. Is that a known issue/missing feature part of a to-do list? It may be worth adding to the changelog, since people may wrongly assume that Ref<SparseMatrix> support implies Ref<SparseVector> support.

Nonetheless, thanks for the great work on that new release!

Best regards,
Comment 1 Gael Guennebaud 2015-09-19 19:53:47 UTC
Thank you for the report. The truth is that I always forgot about SparseVector (not really useful IMO), but yes, Ref<SparseVector> is indeed useful to access to "inner-vectors" of a sparse matrix. So we should add support for it (and Map<SparseVector> too)
Comment 2 Gael Guennebaud 2015-10-26 15:27:36 UTC
Fixed in changeset 7755655e28d6
Comment 3 Nobody 2019-12-04 14:54:35 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance:

Note You need to log in before you can comment on or make changes to this bug.