v0.0-331-g5d7fe52: Factor out DisableSyntaxBasedRanges() subroutine.

Shortening main formatting function for readability.

PiperOrigin-RevId: 304297805

v0.0-320-g2cad9a0: Allow identifier-like symbols for the import alias name.

Fixes crash in verilog::MakeDPIImport() with signature like:
  Check failed: E(leaf.get().token_enum) == expected_token_enum (293 vs. 292)

PiperOrigin-RevId: 303818326

v0.0-310-ga9d1b64: Lint: Make acceptance of anonymous nested structs configurable.

This adds 'allow_anonymous_nested' configuration to the 'typedef-structs-unions'
rule to allow not to require a typedef for inner structs.

In the course of that, implement SyntaxTreeContext::IsInsideStartingFrom()
which starts looking backward the stack starting with an offset.

(As a side effect, make IsInside() to start looking from top of stack
instead of bottom, which is conceptually more aligned of what we expect,
even though it makes only a difference in this case (offset 0))

Fixes #128

PiperOrigin-RevId: 302738764

v0.0-309-g6b58e8f: Fix compile on C++11; fix missing include.

PiperOrigin-RevId: 302729990

v0.0-297-g751d4d8: PR #229: Allow lint configuration to be placed in files

I am opening this early to ask for comments.

Some general info:
* The configuration from file is read after setting up the default configs, but before parsing the invocation arguments. This way the arguments can easily overwrite the configuration from the file
* I think the following should be considered (all of them should be optional):
  * a global configuration file (e.g. `~/.verible_lint.rules`)
  * a local configuration file (e.g. the top directory of a project), this assumes the linter is executed from the top dir of the project
  * any arbitrary file, specified with an argument
  * If we decide to use all of the options listed above we could:
    * combine the global file, local file and file from a flag (in that order), or
    * ignore global file if a local one exists, ignore both if another one is specified with a flag
    * always overwrite the config from files when the same flags are specified with the `-rules` switch
* for now the implementation does some string operations on the file to make the format compatible with the arguments format. The only difference is the settings can be put in separate lines to improve readability. Thanks to this we can reuse the same parsing code

Other options to consider:
* use a completely different format for the configuration (e.g. ini files, with a general `[rules]` section, and more rule-specific configuration)

Please share your thoughts.

CC @hzeller

GitHub PR https://github.com/google/verible/pull/229

Copybara import of the project:

  - 776ca4e4fb9049602175e6ab72e7c31d950b2b42 Allow lint configuration to be placed in files by Tomasz Gorochowik <[email protected]>

Closes #229

PiperOrigin-RevId: 301922115

v0.0-296-gaf5273e: Signal lexical errors during recursive lex-diff.

Diff function now returns a DiffStatus enum instead of a bool to communicate
the nature of the error condition.

VerilogLexicallyEquivalent() is now formulated in terms of the
now-entirely-language-agnostic (functional programming style)
LexicallyEquivalent().
Recursion is no longer hard-coded, but controlled with a std::function.
There is now no need for separate compare-tokens versions of the equivalence
checking function.

Added more test checks to improve raw coverage and mutation coverage.

PiperOrigin-RevId: 301878111

v0.0-291-g3bd3970: Remove unused function.

PiperOrigin-RevId: 301476245

v0.0-285-gc2e5040: PR #231: Add missing macro definitions to fix CI failures

Without this the CI fails. Both with current master and for all new PRs (e.g. #229)

GitHub PR https://github.com/google/verible/pull/231

Copybara import of the project:

  - 7b968f481a209d17980407ad370197fa6f2262fe Add missing macro definitions to fix CI failures by Tomasz Gorochowik <[email protected]>

Closes #231

PiperOrigin-RevId: 301421516

v0.0-273-gaac6cdb

AppendFittingSubpartitions: support alternate flat-singleton partitio…

v0.0-269-g4ecb59b: Parse nonblocking event trigger operator '->>'. LRM 15.5.1

Also factored out a kRepeatControl grammar rule for reuse.

'delay_or_event_control' now matches LRM description.

Renamed event trigger constructs to distinguish between blocking/nonblocking.

Also handle new operator in formatter token_annotator.
Adds new and missing tests for '->' and '->>'.

fixes #227

PiperOrigin-RevId: 299368975