Skip to content

Conversation

@Igor-Lacko
Copy link

Contains versions of the determinize/is_included() algorhiotms using the boost library's bit vectors as opposed to OrdVectors.

… boost, use USE_BOOST=1 (or 0 if not, though that is the default behaviour anyway). Wrapped all code that is dependent on boost (so boost-vector.hh, some algorithms, debug functions, test cases in unit tests and perftests in tests-integration/) into a #ifdef USE_BOOST....#endif block for this to function correctly.
…ning the final states straight away and also passing a size parameter to unify_targets_boost (both cases would probably be resized just once anyway, but in the case of unify_targets_boost which is called a lot of timesit could be a lag on the overall performance)
…ed into a unordered map which will avoid repetead computation of these values
@Adda0
Copy link
Collaborator

Adda0 commented Mar 27, 2025

Hmm, it is a shame so much of the Boost library is needed. This basically means the integration of a subset of the Boost library to Mata is useless, and we can just add Boost as a simple optional dependency, without which certain files using the Boost library will not be compiled. The problem is that then one kind of cannot use the Boost library anywhere in the project reasonably. Boost would need to be a required dependency in order to allow for using the library wherever it might be beneficial...

@Adda0
Copy link
Collaborator

Adda0 commented Mar 27, 2025

@kilohsakul Have a look at how much of a Boost is needed here. Including this into Mata would enlarge the project thousandfold. Any opinions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants