Subject: Re: bug#56682: feature/improved-locked-narrowing 9dee6df39c: Reworked locked narrowing.

From: Eli Zaretskii <[email-masked]>
Date: Wed, 10 May 2023 17:00:35 +0300

> Date: Tue, 09 May 2023 21:48:42 +0000
> From: Gregory Heytings <[email-masked]>
> cc: [email-masked], [email-masked]
> 
> > I'd prefer to use a marker there, but that can be a separate changeset.
> >
> 
> Can you confirm that the attached patch is what you would prefer?  IMHO it 
> is better/clearer to have a single call to XMARKER in 
> 'labeled_restrictions_get_bound', instead of having to repeat it 
> everywhere its return value is used.  The price is indeed that the 
> signature of that (internal) function is unusual.  (Note that we cannot 
> wrap the calls to 'labeled_restrictions_get_bound' in a call to XMARKER, 
> because it can return nil.)

Yes, this is what I meant, but please use marker_position and
marker_byte_position instead of accessing the object directly.

Thanks.