Comments (4)
And that's an old message too, coming from a time when there was not a complete fixpoint computed. In reality there's no inaccuracy left.
The one thing left is: if the sources are coming from a pre-processor, which sprinkled with things like
#1 "eol_detect.ml"
then the location info is going to be inaccurate, and might lead to cycles only for that reason.
The issue in that case is not going to be the cycle, but the incorrect info.
Perhaps I'll just add a warning somewhere that there's the assumption that those line directives are not used.
Btw Q: is there a way to ignore those directives, perhaps as a project compilation setting? That would take care of the issues.
from reanalyze.
Hmm, ok, don't worry about this for now then, I'll hunt some more.
from reanalyze.
Btw Q: is there a way to ignore those directives, perhaps as a project compilation setting? That would take care of the issues.
Well, ocamlformat silently removes them, so for ocaml code there is that. :-)
There must be a reasonably simple pre-processor that would remove them though.
from reanalyze.
Turned off the warning, as it's of little value. Mostly just noise and confusing.
1aa7f46
from reanalyze.
Related Issues (20)
- @inline seems to negate @live/@dead HOT 1
- Records passed to externals can complain about field never being read HOT 1
- Allow configuration via bsconfig.json
- Static Analysis
- `-write` removes trailing newline from modified file
- Binding operators are incorrectly marked dead HOT 1
- Use single dead annotation if entire module is unused
- Awkward record field dead attribute placement with unusual record formatting HOT 3
- Re-exported variant is incorrectly marked dead HOT 1
- Interpret OCaml compiler's unused value declaration warning suppression attribute HOT 1
- Confusing dead code warning at module include HOT 1
- When a function is annotated `@dead` values inside it are reported dead. HOT 10
- Module incorrectly marked dead when contains non-dead type and submodule definitions HOT 1
- @dead annotation breaks rescript compiler on a destructured value HOT 3
- decorating functions in pipe chains? HOT 4
- Dead Types wrt consumed types HOT 7
- False alarms for native projects that generate new files HOT 9
- [Feature Request] Support `globs` for `suppress` and `unsuppress`.
- [Feature request] Integrate with `@deriving({abstract: light})` HOT 13
- Interface of sub module are not seen used HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from reanalyze.