Abstract
Technical debt analysis of procedural languages has not kept up with the growth in popularity of procedural languages. This article provides a perspective from one language: Go. We describe analysis complications and the potential for future developments to help practitioners overcome this gap.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.