Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Z module directly #1329

Merged
merged 53 commits into from
Jan 29, 2024
Merged

Use Z module directly #1329

merged 53 commits into from
Jan 29, 2024

Conversation

karoliineh
Copy link
Member

Solves #1317

@karoliineh karoliineh added the cleanup Refactoring, clean-up label Jan 15, 2024
src/analyses/baseInvariant.ml Fixed Show fixed Hide fixed
src/analyses/baseInvariant.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/arrayDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/arrayDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/intDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/arrayDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/arrayDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/intDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/intDomain.ml Fixed Show fixed Hide fixed
src/cdomain/value/cdomains/intDomain.ml Fixed Show fixed Hide fixed
@karoliineh karoliineh marked this pull request as ready for review January 15, 2024 19:20
@karoliineh karoliineh marked this pull request as draft January 15, 2024 19:26
src/analyses/baseInvariant.ml Outdated Show resolved Hide resolved
src/analyses/baseInvariant.ml Outdated Show resolved Hide resolved
src/cdomain/value/cdomains/intDomain.ml Outdated Show resolved Hide resolved
src/cdomain/value/cdomains/intDomain.mli Show resolved Hide resolved
src/common/util/intOps.ml Outdated Show resolved Hide resolved
unittest/cdomains/intDomainTest.ml Show resolved Hide resolved
@sim642 sim642 added this to the v2.4.0 milestone Jan 23, 2024
@michael-schwarz
Copy link
Member

I think some comments also still refer to bitwise operations where they should now refer to logical operations to be consistent.

(** Logical and: [x && y] *)

val logor : t -> t -> t
val c_logor : t -> t -> t
(** Logical or: [x || y] *)

end
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is one of the places where comments and function names should be made to match.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This matches though. The c_ prefix means it's logical in the C sense, which is what the comment also says.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but e.g. the section headers like Logical Operations and Bit operators are now very confusing after we renamed these functions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confusing how? They still correctly refer to what kind of C operations they're for and include example C expressions.

The confusing thing is OCaml using log prefix for bitwise operations and calls them "bitwise logical" in standard library documentation. All we can do is be consistent with it.

@karoliineh karoliineh marked this pull request as ready for review January 29, 2024 11:00
@sim642 sim642 linked an issue Jan 29, 2024 that may be closed by this pull request
@sim642 sim642 merged commit 9178c43 into master Jan 29, 2024
17 checks passed
@sim642 sim642 deleted the z-module branch January 29, 2024 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Refactoring, clean-up
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use Z module directly
3 participants