|
You are here |
enoent.fr | ||
| | | | |
smyachenkov.com
|
|
| | | | | Kotlin did an amazing job saving and including into its scope most of all valuable Java libraries, frameworks, and tools. But there is one type of tool that can't be easily imported and reused - static code analyzers. Java developers have implemented a lot of tools for code analysis, therefore, if you have worked with Java you might be familiar with some of the following projects: PMD, checkstyle, findbugs, spotbugs, etc. | |
| | | | |
fzakaria.com
|
|
| | | | | Have you encountered the following? > bazel build INFO: Invocation ID: f16c3f83-0150-494e-bd34-1a9cfb6a2e67 WARNING: Build option --incompatible_strict_action_env has changed, discarding analysis cache (this can be expensive, see https://bazel.build/advanced/performance/iteration-speed). INFO: Analyzed target @@com_google_protobuf//:protoc (113 packages loaded, 1377 targets configured). [483 / 845] 13 actions, 12 running Compiling src/google/protobuf/compiler/importer.cc; 3s disk-cache, darwin-sandbox Compiling src/google/protobuf/compiler/java/names.cc; 1s disk-cache, darwin-sandbox Compiling src/google/protobuf/compiler/java/name_resolver.cc; 1s disk-cache, darwin-sandbox Compiling src/google/protobuf/compiler/java/helpers.cc; 1s disk-cache, darwin-sandbox Compiling src/google/protobuf/compiler/objectivec/enum.cc; 1s disk-cache, darwin-sandbox Compiling absl/strings/cord.cc; 1s disk-cache, darwin-sandbox Compiling src/google/protobuf/compiler/objectivec/names.cc; 0s disk-cache, darwin-sandbox Compiling absl/time/internal/cctz/src/time_zone_lookup.cc; 0s disk-cache, darwin-sandbox ... I finally had it with Bazel recompiling protoc ?? The working title for this post: Why the #$@! does protoc keep recompiling! ?? If you are not interested in the story and just want to avoid recompiling protoc, try putting build --incompatible_strict_action_env in your .bazelrc. Checkout Aspect's bazelrc guide for other good tidbits. | |
| | | | |
www.jeremykun.com
|
|
| | | | | Table of Contents As we announced recently, my team at Google has started a new effort to build production-worthy engineering tools for Fully Homomorphic Encryption (FHE). One focal point of this, and one which I'll be focusing on as long as Google is willing to pay me to do so, is building out a compiler toolchain for FHE in the MLIR framework (Multi-Level Intermediate Representation). The project is called Homomorphic Encryption Intermediate Representation, or HEIR. | |
| | | | |
www.syntasso.io
|
|
| | | An IDP is a self-service system with a centralised interface or entry point called an internal developer portal- which is also sometimes referred to as IDP. Through this portal, developers gain access to a pool of tools and resources needed to build, test, and deploy software. | ||