In reference to compiler message:
"function std.math.floor conflicts with std.date.floor ..."
The floor functions in std.math and std.date are
colliding with each other, thus requiring the
necessity to use "std.math.floor(x)" instead
of "floor(x)" in certain cases. I'd call this a
major nuicance, especially when porting certain
C programs to D.
How about renaming the "floor" function in
std.date, since it is not even mentioned in the
Phobos docs?

In reference to compiler message:
"function std.math.floor conflicts with std.date.floor ..."
The floor functions in std.math and std.date are
colliding with each other, thus requiring the
necessity to use "std.math.floor(x)" instead
of "floor(x)" in certain cases. I'd call this a
major nuicance, especially when porting certain
C programs to D.
How about renaming the "floor" function in
std.date, since it is not even mentioned in the
Phobos docs?

Why not use an alias? The whole point of a good module system is, that
it separates symbols into namespaces and allows solving conflicts in an
easy way.
(Even better would be, of course, if conflicting routines from different
modules were automatically handled as overloads of each other. I think
that issue was discussed before?)

In reference to compiler message:
"function std.math.floor conflicts with std.date.floor ..."
The floor functions in std.math and std.date are
colliding with each other, thus requiring the
necessity to use "std.math.floor(x)" instead
of "floor(x)" in certain cases. I'd call this a
major nuicance, especially when porting certain
C programs to D.
How about renaming the "floor" function in
std.date, since it is not even mentioned in the
Phobos docs?

Why not use an alias? The whole point of a good module system is, that
it separates symbols into namespaces and allows solving conflicts in an
easy way.
(Even better would be, of course, if conflicting routines from different
modules were automatically handled as overloads of each other. I think
that issue was discussed before?)

That would work but looking at the floor() in std.date it looks to me like it
should be private.

In reference to compiler message:
"function std.math.floor conflicts with std.date.floor ..."
The floor functions in std.math and std.date are
colliding with each other, thus requiring the
necessity to use "std.math.floor(x)" instead
of "floor(x)" in certain cases. I'd call this a
major nuicance, especially when porting certain
C programs to D.
How about renaming the "floor" function in
std.date, since it is not even mentioned in the
Phobos docs?

Why not use an alias? The whole point of a good module system is, that
it separates symbols into namespaces and allows solving conflicts in an
easy way.
(Even better would be, of course, if conflicting routines from different
modules were automatically handled as overloads of each other. I think
that issue was discussed before?)

That would work but looking at the floor() in std.date it looks to me like
it
should be private.