- **labels**:  --> Fixed_2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

```text
commit d6956e8ed6da831574cd9bcadb05ac0c47c84a07
Author: Dan Eble <[email protected]>
Date:   Thu Jan 30 17:38:20 2020 -0500
```



---

** [issues:#5713] Remove likely dead code from set_property_from_event**

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Fri Jan 31, 2020 01:06 AM UTC by Dan Eble
**Last Updated:** Tue Feb 04, 2020 06:20 AM UTC
**Owner:** Dan Eble


I couldn't find input that would reach this block.  With this block out
of the way, type_check_assignment () will vet all values.  Its current
behavior is to assert () that the value is defined.

https://codereview.appspot.com/557260047


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to