Laurent Le Brun

Results 51 issues of Laurent Le Brun

There are more cases where we could replace a float with an int (`1` instead of `1.`). See discussion in https://www.pouet.net/topic.php?which=12089&page=1 Quote from the spec: > The OpenGL Shading Language...

The behavior is documented (https://github.com/laurentlb/Shader_Minifier#unused-local-variables), but it can be risky to remove the initialization code of a variable that is not used. Code example: ```glsl out vec4 outcolor; float glow...

We should replace `+= 1.` with `++`. This should work both on ints and on floats. Same for the `--` operator. ```glsl a += 1.; ```

1. Even if we need the variable f, we can inline the last assignment here (since A is not used afterwards): ```glsl f+=r*smoothstep(.5,-1.,sunDir.y); return f; ``` 2. We could get...

```glsl in float a; in vec2 b; in float c; ``` could be minified as: ```glsl in float a,c; in vec2 b; ``` Right now, we merge only adjacent declarations...

We need an option to rename variables in a consistent way. For example, if there are two variables "foo" in two different functions, or even two different files, they should...

It would be nice to allow this: ``` ocaml_native_binary( name = "ocaml", srcs = "hello.ml", ) ``` In other words, when there's only one source file, it should be used...

Hi, Do you know how this ruleset compares to rules_reason? https://github.com/ostera/rules_reason There seems to be some overlap (see `ocaml_native_binary` and `ocaml_bytecode_binary`). cc @ostera

https://buildkite.com/bazel/tools-jvm-autodeps/builds/39#712e88ad-9654-4d68-bf60-4ae43b98c785 ``` ERROR: /var/lib/buildkite-agent/builds/buildkite-worker-ubuntu1604-java8-vmhn-1/bazel/tools-jvm-autodeps/BUILD:8:1: Couldn't build file jdk_android_builtin_class_names.txt: Executing genrule //:jdk_android_builtin_class_names failed (Exit 1) 2018/07/09 07:39:57 error opening file external/local_jdk/jre/lib/rt.jar: open external/local_jdk/jre/lib/rt.jar: no such file or directory ``` Seems to...

Some pages are accessible only from the footer (which is easy to miss). In particular, the [FAQ](https://www.bazel.build/faq.html) and the [support policy](https://www.bazel.build/support.html) should be moved to a proper menu.