id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
13374	Boykov Kolmogorov warning with float	cyril.novel@…	Jeremiah Willcock	"In boykov_kolmogorov_max_flow.hpp, some values put in property_map are integer :

{{{
l.176             put(m_res_cap_map, from_source, 0);
l.190              put(m_dist_map, current_node, 1);
l.196              put(m_res_cap_map, to_sink, 0);
l.202              put(m_dist_map, current_node, 1);
l.208              put(m_res_cap_map, from_source, 0);
l.217            put(m_dist_map, current_node, 1);
l.228            put(m_dist_map, current_node, 1);
}}}

It causes a C4244 warning in property_map/property_map.hpp (l.310) when using floating distance and floating cost. An easy way to prevent this is to patch as follow:

{{{
l.176             put(m_res_cap_map, from_source, tEdgeVal(0));
l.190              put(m_dist_map, current_node, tDistanceVal(1));
l.196              put(m_res_cap_map, to_sink, tEdgeVal(0));
l.202              put(m_dist_map, current_node, tDistanceVal(1));
l.208              put(m_res_cap_map, from_source, 0);
l.217            put(m_dist_map, current_node, tDistanceVal(1));
l.228            put(m_dist_map, current_node, tDistanceVal(1));
}}}

Compiler: VS2017"	Bugs	new	To Be Determined	graph	Boost 1.63.0	Problem