change the init-exe example to avoid confusion with ReleaseFast and std.log.info

[M0n7y5]

Zig Version

0.9.0-dev.1352+6d6cf5984

Steps to Reproduce

just init simple zig project and build it with -Drelease-fast=true or -Drelease-small=true

const std = @import("std");

pub fn main() anyerror!void {
    std.log.info("All your codebase are belong to us.", .{});
}

Expected Behavior

Produced binary should print All your codebase are belong to us.

Actual Behavior

It doesn't print anything. Instead it just exits immediately.

[leecannon]

Only log messages equal to or higher than the log level will be printed and the default log level of release modes is higher than info:

zig/lib/std/log.zig

Lines 117 to 122 in e851d89

	pub const default_level: Level = switch (builtin.mode) {
	.Debug => .debug,
	.ReleaseSafe => .notice,
	.ReleaseFast => .err,
	.ReleaseSmall => .err,
	};

To override this in the main file add pub const log_level = std.log.Level.info

However it does make sense to still treat this as an issue as it would make sense to note this in a comment in the file generated by init-exe. As this is definitely unexpected.

[M0n7y5]

So this is intended behavior? Also i was trying to inspect generated binary using IDA , but for some reason generated PDB files is crashing IDA once its loaded.

[M0n7y5]

To override this in the main file add pub const log_level = std.log.LogLevel.info

LogLevel doesn't exist so after looking into log.zig i found out that enum is just Level.
pub const log_level = std.log.Level.info;
Now it compiles without errors.

[leecannon]

Yes, by default info level log messages are not emited in release modes. It is unfortunate that due to this the template executable produces no output when built non-debug.

To improve this there are really only three options:

• Add a comment to the file generated by init-exe explaining log levels (including the different defaults based on build mode), the only negitive to this is a bit of additional noise, but this has precedence with the comments in the generated build.zig
• Use a higher log level message, it would need to be atleast err to be output on every build mode, the problem with this is a "hello world" message doesnt make sense to be logged at error or higher
• Directly write to stdout/std.debug.print, this is what the generated file contained before being replaced with the current call to std.log, std.log is a useful system with many features (scoped messages, different log levels per scope, libraries can mindlessly use it without worrying as the application can chosse to filter its messages out, custom logging implementation) due to these prefering to use std.log in the template to prompt its usage is a good idea

[Prince213]

I think it's an overkill to use std.log for a template executable. Maybe we should do something simple, like writing to stdout directly.

[g-w1]

It was decided to log because this is better scaffolding for larger projects.

[Prince213]

If the intent is to remind users to use std.log, then it should be stated in the docs, not in a simple example program that is expected to do something simple.

[wizzard0]

To me, a simplest improvement would be to add a comment to the generated source file, saying "log messages with info level would not be emitted in ReleaseFast, if you intended to use stdout to output some processing results, use X (link to example)"

(edit): Also, maybe remove [windows] from the issue title? Looks cross-platform to me