Nicolas Goy

I would like to propose the following solution: - default language is optional, if present, it would be at `/`, like now - a new option, perhaps `language.XX.force_output` if set...

There is also the situation where / is a welcome screen with a language picker. So it would be a "language neutral" page For twice the output, there are some...

The option to force the namespacing of the default language and have HTML redirects is fine to me, I made other proposition because I thought it was not liked. Maybe...

I think it should stay because of: ``` var foo = T{}; ... foo = T{} // make it clear what we are assigning. ``` I also do not see...

I have the same issue, so I went the helper route too. I think the simpler fix would be to implement something like include("path") that would act more like a...

To summarize my requirements/wishes: - I need to be able to bundle a package (let's call it a component!) to be reused in someone's app, I don't want them to...

I understand your points and even if it's not my ideal world, I agree with you. I'd just say that most of my current work targets enterprise customer that will...

I think this is another problem, customization in elm should be handled by passing view functions to the component. On November 24, 2017 11:43:07 AM GMT+01:00, feluxe wrote: >Sorry for...

I have a mostly neutral stance on this proposal. Just a though on the name, let's have the following code: ```zig pub fn build_something() @ResultType() { var something: @ResultType() =...

I agree with @InKryption that there are many places that function instance can be created transparently. I think this feature would be similar to functions accepting `anytype`. On embedded platform,...