A typed-specific sequencer pointer p_sequencer tracking issue

In reply to cgales:

In reply to Geet:
As soon as you use a p_sequencer, you are restricting what sequencer your sequences can run on. By not using p_sequencer, you can run your sequences on any appropriately typed sequencer.

Hi cgales,

In case of m_sequencer also we used to provide a path to sequencer in start method.

//From test
task run_phase(uvm_phase phase);
phase.raise_objection(this);
seq.start(env.mem_agnt.sequencer); //path to sequencer
phase.drop_objection(this);
endtask : run_phase

I’m not sure I get this 100% in re-usability term.