DreamPearl commented on a change in pull request #309:
URL: https://github.com/apache/qpid-proton/pull/309#discussion_r611878305



##########
File path: cpp/src/delivery.cpp
##########
@@ -40,6 +42,7 @@ namespace proton {
 
 delivery::delivery(pn_delivery_t* d): transfer(make_wrapper(d)) {}
 receiver delivery::receiver() const { return make_wrapper<class 
receiver>(pn_delivery_link(pn_object())); }
+tag delivery::tag() const { return make_wrapper<class 
tag>(pn_delivery_tag(pn_object())); }

Review comment:
       I started seeing error after make clean :( will take a look again.
   
   ```In file included from /home/rakhi/qpid-proton/cpp/src/delivery.cpp:28:
   /home/rakhi/qpid-proton/cpp/src/proton_bits.hpp: In instantiation of ‘U 
proton::make_wrapper(typename proton::internal::wrapped<T>::type) [with U = 
proton::tag; typename proton::internal::wrapped<T>::type = pn_bytes_t]’:
   /home/rakhi/qpid-proton/cpp/src/delivery.cpp:45:88:   required from here
   /home/rakhi/qpid-proton/cpp/src/proton_bits.hpp:159:91: error: cannot 
convert ‘proton::internal::wrapped<proton::tag>::type’ {aka ‘pn_bytes_t’} to 
‘proton::internal::wrapped<proton::tag>::type*’ {aka ‘pn_bytes_t*’}
     159 | U make_wrapper(typename internal::wrapped<U>::type t) { return 
internal::factory<U>::wrap(t); }
         |                                                                      
                     ^
         |                                                                      
                     |
         |                                                                      
                     proton::internal::wrapped<proton::tag>::type {aka 
pn_bytes_t}
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to