Refactor AcceptWay further into a dynamic structure about graphhopper HOT 3 CLOSED

Every encoder requires some storage (at the moment this is always 8 bits per encoder, but configurable). And the flag is an integer which limits the active encoders in one graph to only 4. One could extend that to more (e.g. via two flag integers) but I'm not sure if that would be useful. I would rather concentrate on less vehicles with more correct routes. (I mean having lots of well configured encoders of which only 4 can be active)

from graphhopper.

Agreed, 4 are enough.. What I mean is to have lets say 6 well-encapsulated encoders, 4 of which can be active at a time. But select them with some register() method and iterate over a list of encoders instead of hardcoded if( car) if (bike ) etc.

Should be fairly simple. In the encoders, only the shift-value must be assigned dynamically when registering so they will use the right bits and are compatible with any other encoder.

from graphhopper.

I agree, but we should test if a loop over not soo many entries has the same speed. But I bet the JIT will unroll the loop and make it fast ..

from graphhopper.