Behind the scenes a scientific number notation is always represented as a float internally. The reason is the varying number range as an integer only maps to a fixed value range, let’s say 2^32 values. The scientific representation is similar to the floating representation with significant and exponent. Further details you can lookup in https://en.wikipedia.org/wiki/Floating_point. … Read more
Using assign with a math filter is correct. See this thread on GitHub, and this blog post. Variables created through {% capture %} are strings. When using assign, either of these options should give you a number: {% assign var1 = var1 | plus: 0 %} {% assign var2 = var2 | times: 1 %} … Read more
(&str).as_bytes gives you a view of a string as a &[u8] byte slice (that can be called on String since that derefs to str, and there’s also String.into_bytes will consume a String to give you a Vec<u8>. Use the .as_bytes version if you don’t need ownership of the bytes. fn main() { let string = … Read more
This is not a bug. fmt.Println() requires a []interface{} type. That means, it must be a slice of interface{} values and not “any slice”. In order to convert the slice, you will need to loop over and copy each element. old := flag.Args() new := make([]interface{}, len(old)) for i, v := range old { new[i] … Read more