Skip to content

Conversation

@ednolan
Copy link
Member

@ednolan ednolan commented Jan 4, 2026

No description provided.

@ednolan ednolan requested a review from tzlaine as a code owner January 4, 2026 20:34
@ednolan ednolan force-pushed the enolan_exemplarify2 branch from ac3f091 to 7bedbab Compare January 4, 2026 20:37
@coveralls
Copy link

coveralls commented Jan 4, 2026

Coverage Status

coverage: 100.0%. remained the same
when pulling f5507d4 on enolan_exemplarify2
into e5d92f5 on main.

@ednolan ednolan force-pushed the enolan_exemplarify2 branch 2 times, most recently from 756dedc to 0f8f41d Compare January 4, 2026 23:24
@ednolan ednolan force-pushed the enolan_exemplarify2 branch from 0f8f41d to f5507d4 Compare January 4, 2026 23:38

add_subdirectory(include/beman/transform_view)

include(CTest)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
include(CTest)

This is handled in line 51 (enable_testing includes ctest) under the condition that tests are being built

$ build/gcc-release/examples/beman.transform_view.examples.transform_view_direct_usage
lower
The `debug` presets are designed to aid development, so it has debugging
instrumentation enabled and many sanitizers enabled.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I sort of dislike that we've removed the specifics that were put here....


<details>
<summary> Use beman.transform_view directly from C++ </summary>

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The statement below is valid -- we really need to separate the readme for building versus 'using in your project'.

Copy link
Collaborator

@tzlaine tzlaine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all seems fine to me. Are Jeff's comments blocking this? I'm unclear if I should merge it as-is.

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.

5 participants