← Back to context Comment by mort96 2 days ago What's the explanation for paths to q00.rs-q36.rs being in the binary? 5 comments mort96 Reply malisper 2 days ago It was included by mistake. It was code that was in our repo that wasn't explicitly marked as test code, so it got included in the binary. f311a 2 days ago How? Compilators eliminate unused code. malisper 2 days ago I got it slightly wrong. It was code that you could run with an environment variable: PGRUST_GRAVITY_IRPROBE. It still wasn't intended to be part of the actual binary. 2 replies →
malisper 2 days ago It was included by mistake. It was code that was in our repo that wasn't explicitly marked as test code, so it got included in the binary. f311a 2 days ago How? Compilators eliminate unused code. malisper 2 days ago I got it slightly wrong. It was code that you could run with an environment variable: PGRUST_GRAVITY_IRPROBE. It still wasn't intended to be part of the actual binary. 2 replies →
f311a 2 days ago How? Compilators eliminate unused code. malisper 2 days ago I got it slightly wrong. It was code that you could run with an environment variable: PGRUST_GRAVITY_IRPROBE. It still wasn't intended to be part of the actual binary. 2 replies →
malisper 2 days ago I got it slightly wrong. It was code that you could run with an environment variable: PGRUST_GRAVITY_IRPROBE. It still wasn't intended to be part of the actual binary. 2 replies →
It was included by mistake. It was code that was in our repo that wasn't explicitly marked as test code, so it got included in the binary.
How? Compilators eliminate unused code.
I got it slightly wrong. It was code that you could run with an environment variable: PGRUST_GRAVITY_IRPROBE. It still wasn't intended to be part of the actual binary.
2 replies →