Gauthier Segay

probable location of the bug, or the callsite which gives some display settings as input parameter: https://github.com/dotnet/fsharp/blob/2046609d307e5616f8288cf9b4d0a2c04a4c17ef/src/fsharp/NicePrint.fs#L782-L804

@RaoulHC, thanks for all the pointers (erm, targets)! I was just looking in the older lexer and got hopeful seeing both `record` and `structure`, giving `-v 77l` helps but I'm...

@RaoulHC thanks. I've started something in #305, note that in the codebase I'm looking at, I also have things like `[allocatable](:)`. Intel Fortran compiler support a bunch of those qualifiers,...

```fortran module mixed_idioms_structure_and_records_declarations implicit none structure /MyThing/ integer field1 real field2 end structure contains subroutine something () record /MyThing/ myThings[allocatable](:) integer i, max max = 100 allocate(myThings(max)) do i =...

@RaoulHC thanks for all the feedback, ok I was able to get things to type check again in my branch, the default parsers instantiation is a bit gnarly :) Understood...

I'm trying to add this in Free/Lexer.x ```haskell "structure" / { legacyDECStructureP } { toSC scT >> addSpan TStructure } "endstructure" / { legacyDECStructureP } { toSC scT >> addSpan...

Made some progress in #305; to parse my example, the remaining thing is the `[allocatable]` attribute. This syntax doesn't seem to be documented on intel website https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2023-0/allocatable.html. I think it...

> I just tried to understand what used to happen here as currently, I sometimes see only partial refresh of source code highlighting, leading to parts staying grey/white-ish. Seeing this...

Would it make sense to nudge the CI here and maybe look into adjustments in dotnet/fsharp that would make it easy to test the preview compiler?

The main thing I remember was Don wasn't super eager we use F#+ as motivator for evolving the compiler / language design (on areas like overload resolution, etc.), but I...