Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mappend PrimitiveArrays or PrimitiveStreams of varying topologies. #26

Open
PiotrJustyna opened this issue Apr 17, 2016 · 1 comment
Open

Comments

@PiotrJustyna
Copy link

PiotrJustyna commented Apr 17, 2016

First of all, I appreciate your work on the library. I've been playing with it for the last few weeks and I really like it so far.

While experimenting with the library's capabilities, I stumbled across combining PrimitiveArrays (or PrimitiveStreams) of varying topologies, e.g.

  • triangles + points
  • points + lines
  • etc.

I'm playing with rendering (any-topology) objects and their per-vertex normal vectors (represented always as lines) and could really use that feature. Is this something you have ever considered implementing? If not, is it because what I'm after can be achieved with some other mechanism?

Thanks and keep up the great work!

@PiotrJustyna PiotrJustyna changed the title Mappend PrimitiveArrays or PrimitiveStream of varying topologies. Mappend PrimitiveArrays or PrimitiveStreams of varying topologies. Apr 17, 2016
@plredmond
Copy link
Contributor

Since the topologies of PrimitiveArrays and PrimitiveStreams and similar are represented as a type parameter, they're distinct types. As a result, they won't work with the mappend function which requires both of its arguments to be of the same type. This is pretty core to GPipe's design and isn't likely to change.

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

No branches or pull requests

2 participants