Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-08-09 Thread Mark Wielaard
Hi, On Sat, Aug 07, 2021 at 03:01:39AM +0200, Mark Wielaard wrote: > > Sorry for lack of reply on this. After looking into this and also > > getting Arthur Cohen to review, I think: > > > > * Token passing: If we end up using the token for more than the > > location this might be useful but

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-08-08 Thread Philip Herron
On 07/08/2021 02:01, Mark Wielaard wrote: > On Fri, Aug 06, 2021 at 04:23:27PM +0100, Philip Herron wrote: >> On 05/08/2021 20:37, Mark Wielaard wrote: >>> Hi, >>> >>> On Fri, Jul 30, 2021 at 03:03:13AM +0200, Mark Wielaard wrote: That variant is attached and can also be found here: https

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-08-06 Thread Mark Wielaard
mment to the function prototypes in rust-parse.h about the passed in pratt_parsed_token. https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=pass-pratt-parse-token Cheers, Mark >From 1c139cbaa71c2928ca747fa26dc776699937280a Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Thu, 29 Jul 2

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-08-06 Thread Philip Herron
On 05/08/2021 20:37, Mark Wielaard wrote: > Hi, > > On Fri, Jul 30, 2021 at 03:03:13AM +0200, Mark Wielaard wrote: >> That variant is attached and can also be found here: >> https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=pass-pratt-parse-loc >> The original is also here: >> https://code.w

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-08-05 Thread Mark Wielaard
Hi, On Fri, Jul 30, 2021 at 03:03:13AM +0200, Mark Wielaard wrote: > That variant is attached and can also be found here: > https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=pass-pratt-parse-loc > The original is also here: > https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=pass-pra

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-07-29 Thread Mark Wielaard
Hi, On Thu, Jul 29, 2021 at 05:18:50PM +0200, Thomas Schwinge wrote: > On 2021-07-29T12:55:38+0200, Mark Wielaard wrote: > > On Thu, 2021-07-29 at 09:25 +0800, The Other via Gcc-rust wrote: > >> But isn’t it overkill to pass the token in instead of just the > >> location? You can avoid a fairly e

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-07-29 Thread Thomas Schwinge
Hi! On 2021-07-29T12:55:38+0200, Mark Wielaard wrote: > On Thu, 2021-07-29 at 09:25 +0800, The Other via Gcc-rust wrote: >> I think the core idea of this patch (fixing locations) is very >> important and useful. Agreed. >> But isn’t it overkill to pass the token in instead of just the >> locati

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-07-29 Thread Mark Wielaard
Hi Joel, On Thu, 2021-07-29 at 09:25 +0800, The Other via Gcc-rust wrote: > I think the core idea of this patch (fixing locations) is very > important and useful. > > But isn’t it overkill to pass the token in instead of just the > location? You can avoid a fairly expensive shared_ptr copy by doi

Re: [PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-07-28 Thread The Other via Gcc-rust
I think the core idea of this patch (fixing locations) is very important and useful. But isn’t it overkill to pass the token in instead of just the location? You can avoid a fairly expensive shared_ptr copy by doing so. > On 29 Jul 2021, at 6:13 am, Mark Wielaard wrote: > > The pratt parser

[PATCH] Pass pratt parsed token to expr parser functions to fix expr locus

2021-07-28 Thread Mark Wielaard
The pratt parser skips the first token of an expression before invoking the actual expression parsing function. This makes getting the correct starting location of a pratt parsed expression hard. The "correction" of the location by subtracting an integer is often wrong (since there may be arbitrary