jackalcooper

jackalcooper

Is it possible to define recursive/inter-dependent parse combinators in NimbleParsec?

I’m trying to parse Zig source with NimbleParsec and come across some cases like these:

  • in the definition of containerdeclarations, it uses itself
containerdeclarations = choice(
  testdecl |> concat(containerdeclarations),
  toplevelcomptime |> concat(containerdeclarations),
  optional(doc_comment) |> optional(keyword_pub) |> concat(topleveldecl) |> concat(containerdeclarations)
)
  • expr uses asmexpr indirectly while asmexpr uses expr
asmexpr =
  keyword_asm
  |> optional(keyword_volatile)
  |> concat(lparen)
  |> concat(expr)
  |> optional(asmoutput)
  |> concat(rparen)
primaryexpr =
  choice([
    asmexpr,
    ifexpr,
    keyword_break |> optional(breaklabel) |> optional(expr),
    keyword_comptime |> concat(expr),
    keyword_nosuspend |> concat(expr),
    keyword_continue |> optional(breaklabel),
    keyword_resume |> concat(expr),
    keyword_return |> optional(expr),
    optional(blocklabel) |> concat(loopexpr),
    block,
    curlysuffixexpr
  ])

prefixexpr = repeat(prefixop) |> concat(primaryexpr)

multiplyexpr = prefixexpr |> optional(multiplyop |> concat(prefixexpr))

additionexpr = multiplyexpr |> optional(additionop |> concat(multiplyexpr))

bitshiftexpr = additionexpr |> optional(bitshiftop |> concat(additionexpr))

bitwiseexpr = bitshiftexpr |> optional(bitwiseop |> concat(bitshiftexpr))

compareexpr = bitwiseexpr |> optional(compareop |> concat(bitwiseexpr))

boolandexpr = compareexpr |> optional(keyword_and |> concat(compareexpr))

boolorexpr = boolandexpr |> optional(keyword_or |> concat(boolandexpr))

expr = boolorexpr

Marked As Solved

kip

kip

ex_cldr Core Team

Yes, you can have recursive combinators. But they need to be defined as defparsec in order to create their own context. They will need to be defined in their own module since they become functions. Something like (not complete):

defmodule Combinators do
  import NimbleParsec
  
  defparsec :asmexpr, 
    keyword_asm
    |> optional(keyword_volatile)
    |> concat(lparen)
    |> parsec(:expr)
    |> optional(asmoutput)
    |> concat(rparen)
    
  defparsec :primaryexpr,
    choice([
      parsec(:asmexpr),
      ifexpr,
      keyword_break |> optional(breaklabel) |> optional(parsec(:expr)),
      keyword_comptime |> parsec(:expr),
      keyword_nosuspend |> parsec(:expr),
      keyword_continue |> optional(breaklabel),
      keyword_resume |> parsec(Lexpr),
      keyword_return |> optional(parsec(:expr)),
      optional(blocklabel) |> concat(loopexpr),
      block,
      curlysuffixexpr
    ]) 

  # Other combinators
end

Also Liked

jackalcooper

jackalcooper

update:

100phlecs

100phlecs

This may be of interest to you, though I’m not certain on its status: GitHub - E-xyza/zig_parser: Zig Parser for Elixir · GitHub

It is created with GitHub - ityonemo/pegasus: peg -> nimbleparsec · GitHub

An unrelated thought, but curious of the advantages and disadvantages of the PEG route vs a traditional lexer + parser

ityonemo

ityonemo

It works (well enough for my zigler 0.10.x development branch) and is currently designed to parse zig 0.10.x

Last Post!

jackalcooper

jackalcooper

@ityonemo
the problematic expr seems not to be covered by the fix in the last commit

pub const __LDBL_MAX__ = @as(c_longdouble, 1.18973149535723176502e+4932);

https://github.com/ityonemo/zig_parser/issues/2#issuecomment-1365148468

Where Next?

Trending in Questions Top

lanycrost
Hi everyone! I need implement if…else if…else condition from my elixir code, and anymore of this control flow structures not work proper...
New
senggen
Erlang/OTP 25 [erts-13.2.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] 15:22:35.803 [error] gen_event {lager_file_backend...
New
hariharasudhan94
Lets say I have map like this fetching from my database %{"_id" => #BSON.ObjectId<58eb1a7a9ad169198c3dXXXX>, "email" => ...
New
tj0
I’ve been following the steps here for the upgrade from 1.6 to 1.7 and it has gone relatively smoothly all the way till the phoenix_view ...
New
cgraham
Hi! What is currently the best library/method for parsing text and tabular data out of PDF files in Elixir or Erlang?
New
stefanchrobot
Hi, I need a way to handle data migrations in my application. I found an article by @wojtekmach about manual migrations: Automatic and ma...
New
stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
kip
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
webofbits
Squid Mesh is an open source workflow automation runtime for Elixir applications. It is aimed at Phoenix and OTP apps that want to defin...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
kip
In 2021 I started a new library called Tempo with the objective of modelling time as a set of intervals - not as instants. In 2022 I gave...
New

We're in Beta

About us Mission Statement